Why is life with Red Hat 9 a pain in the hind side?
  • Avatar

    hserus — Dec 17, 2003 10:55:08 AM — #

    Because it is?
    • Avatar

      Kiran Jonnalagadda — Dec 17, 2003 11:03:57 AM — #

      How am I supposed to deal with this?

      [root@mahiti root]# rpmbuild -ta courier-imap-2.2.1.tar.bz2
      Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.27907
      + umask 022
      + cd /usr/src/redhat/BUILD
      + LANG=C
      + export LANG
      + LANG=C
      + export LANG
      + cd /usr/src/redhat/BUILD
      + rm -rf courier-imap-2.2.1
      + /usr/bin/bzip2 -dc /root/courier-imap-2.2.1.tar.bz2
      + tar -xf -
      + STATUS=0
      + '[' 0 -ne 0 ']'
      + cd courier-imap-2.2.1
      ++ /usr/bin/id -u
      + '[' 0 = 0 ']'
      + /bin/chown -Rhf root .
      ++ /usr/bin/id -u
      + '[' 0 = 0 ']'
      + /bin/chgrp -Rhf root .
      + /bin/chmod -Rf a+rX,g-w,o-w .
      + CFLAGS=-O2 -g -pipe -march=i386 -mcpu=i686
      + export CFLAGS
      + CXXFLAGS=-O2 -g -pipe -march=i386 -mcpu=i686
      + export CXXFLAGS
      + FFLAGS=-O2 -g -pipe -march=i386 -mcpu=i686
      + export FFLAGS
      + ./configure --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --target=i386-redhat-linux-gnu --program-prefix= --prefix=/usr/lib/courier-imap --exec-prefix=/usr/lib/courier-imap --bindir=/usr/lib/courier-imap/bin --sbindir=/usr/lib/courier-imap/sbin --sysconfdir=/usr/lib/courier-imap/etc --datadir=/usr/lib/courier-imap/share --includedir=/usr/lib/courier-imap/include --libdir=/usr/lib/courier-imap/lib --libexecdir=/usr/lib/courier-imap/libexec --localstatedir=/var/run --sharedstatedir=/usr/lib/courier-imap/com --mandir=/usr/lib/courier-imap/man --infodir=/usr/share/info --with-redhat --with-authdaemonvar=/var/run/authdaemon.courier-imap --enable-unicode=iso-8859-1,utf-8
      checking for i686-pc-linux-gnu-gcc... no
      checking for gcc... gcc
      checking for C compiler default output... a.out
      checking whether the C compiler works... yes
      checking whether we are cross compiling... no
      checking for suffix of executables...
      checking for suffix of object files... o
      checking whether we are using the GNU C compiler... yes
      checking whether gcc accepts -g... yes
      checking for gcc option to accept ANSI C... none needed
      checking for gawk... gawk
      checking for a BSD-compatible install... /usr/bin/install -c
      checking whether ln -s works... yes
      checking whether make sets $(MAKE)... yes
      checking for perl5... no
      checking for perl... /usr/bin/perl
      checking for sysconftool...... ././sysconftool
      checking for env... /bin/env
      checking whether build environment is sane... yes
      checking for style of include used by make... GNU
      checking dependency style of gcc... gcc3
      configure: WARNING: === Do not compile Courier-IMAP as root. Compile
      configure: WARNING: === Courier-IMAP as a non-root user then su to
      configure: WARNING: === root before running make install. You must now
      configure: WARNING: === remove this entire directory and then extract the
      configure: WARNING: === source code from the tarball as a non-root user
      configure: WARNING: === and rerun the configure script. If you have read
      configure: WARNING: === the INSTALL file you should have known this. So
      configure: WARNING: === you better read INSTALL again.
      configure: error: aborted.
      error: Bad exit status from /var/tmp/rpm-tmp.27907 (%prep)


      RPM build errors:
      Bad exit status from /var/tmp/rpm-tmp.27907 (%prep)
      [root@mahiti root]#


      I can't build as root. I can't build as non-root. Ready-made RPMs are not available.
      • Avatar

        hserus — Dec 17, 2003 11:08:26 AM — #

        You need this -
        --disable-root-check

        Also consider adding --enable-workarounds-for-imap-client-bugs

        It will help you, believe me.

        --srs
        • Avatar

          Kiran Jonnalagadda — Dec 17, 2003 11:22:29 AM — #

          That helped. Thanks. Was going to report a bug in the spec file, then discovered this FAQ item: http://www.inter7.com/courierimap/FAQ.html#rpm

          I miss the simplicity of life with Debian Unstable. Or of having someone else do the dirty work.

          Oh wait, new error:

          ...
          Making check in imap
          make[1]: Entering directory `/usr/src/redhat/BUILD/courier-imap-2.2.1/imap'

          Error: --with-trashquota or the --enable-workarounds-for-imap-client-bugs
          option was specified to the configure script.

          As INSTALL told you, make check fails if these options are used, and I wasn't
          kidding when I wrote it. Reconfigure and rebuild without these options, then
          rerun make and make check. If make check passes, reconfigure again with your
          original options, and proceed with installing this server. Have fun!

          make[1]: *** [check-am] Error 1
          make[1]: Leaving directory `/usr/src/redhat/BUILD/courier-imap-2.2.1/imap'
          make: *** [check-recursive] Error 1
          error: Bad exit status from /var/tmp/rpm-tmp.91607 (%build)


          RPM build errors:
          Bad exit status from /var/tmp/rpm-tmp.91607 (%build)


          Bah!
          • Avatar

            hserus — Dec 17, 2003 11:25:10 AM — #

            Start with a clean install. And forget make check, maybe.

            Can I suggest freebsd? More MacOS-ish (and in fact the ports tree in freebsd has been ported to OSX as "darwinports" by Jordan Hubbard).
            • Avatar

              Kiran Jonnalagadda — Dec 17, 2003 11:29:35 AM — #

              I just moved *.seacrow.com out of FreeBSD. Setting up mail on the new box now. The choice of RH9 wasn't mine.
              • Avatar

                hserus — Dec 17, 2003 11:35:34 AM — #

                that simply sucks.
        • Avatar

          Kiran Jonnalagadda — Dec 17, 2003 11:27:28 AM — #

          Rebuilding with make check disabled. So far so good.
      • Avatar

        bluesmoon — Dec 17, 2003 11:48:12 AM — #

        why can't you build as non-root? I build all my rpms as non-root. Just change ownership of /usr/src/redhat to yourself.
        • Avatar

          hserus — Dec 18, 2003 10:42:09 AM — #

          Why? Just define the source directory for your rpms to something in your homedir .. /home/redhat/ or something. Far better and breaks things less.
  • Avatar

    tsk1979 — Dec 17, 2003 2:31:17 PM — #

    I know why
    Actually Red Hat wants to be just like windows. So for your pleasure and pain they have also tried to make windoze like nuances a part of their system :). They have been sucessful and congrats. And Jace, congrats to you too, finally something other than bikes gave you pain there!

    I am laughing now, coz i zapped my fedora core to kingdom come. And now i am at peace with the universe.

    What I am running. Well its the devils own till mandrake 9.2 tommorow :)

    And why did i zap fedora. Thats a long story, maybe some day on my journal!!
  • Avatar

    tushar — Dec 19, 2003 5:10:11 AM — #

    Pichwaade mein dard
    I tried RH9 on one of my boxen, for lack of choice. Took me all night to set up mail because my only option apart from doing everything from source, was to use the qmail-toaster package. This is more trouble than its worth and all the bells and whistles didn't work as intended.

    I went back to 7.2 for a new box, with no problems. I'll use it as long as I can keep it hole-free. After that,

    # cd /usr/ports/mail/qmail
    # make install

Leave a Reply

You can respond with a photo by tagging it on Flickr with