port hangs building coreutils (?)

[michele@…]

I run "sudo port install qt3 kdelibs3" on a Powerbook G4. As a result qt3 was built in about 4 hours without any problem. After that the computer built aspell, libiconv, gettext, p5-locale-gettext, help2man, libtool, m4, autoconf, bzip2, flex, glib2, hicolor-icon-theme, jasper, libart_lgpl, libidn, libxml2, libxslt, ncursesw, ncurses, readline, lua, openexr, openssl, pcre, and tiff. Then it run for about 11 hours trying to build coreutils (CTRL+C-ed at that point).

I should mention that this is the second time I try to build kdelibs3. The first time I got stuck with an mtree violation message while building "lua" (see ticket #12503).

After the "lua" mantainer mentioned he fixed the problem and suggsted to try again I removed and reisntalled macports. The second time around I did not have any problem with "lua".

I guess my main question is: is it reasonable to expect that the building of some of the libraries/packages mentioned in this message may take a long LONG time on my laptop? And what does long LONG mean? Is 24 hours a short time for some of these processes?

[afb@…]

Can't reproduce this. coreutils builds in a reasonable amount of time on 10.4.10

[hanche]

Happened to me too. It was hanging during the compilation of lib/sha256.c (I killed the compiler after 87 minutes). I compiled it manually, by copying the failed command line with the -O2 flag removed, and it compiled in seconds. Had to do the same with sha512.c, and now the rest of the build is moving along nicely. Port version 1.520, macosx 10.4.10 on powerpc (12 inch powerbook G4).

[hanche]

I just wanted to state that the bug is still there. It probably depends on what gcc version is in use. I am seeing it with Apple's gcc 4.0.0 20041026. That's kind of old, maybe I need to upgrade? Anyway, my current workaround is to wait for the build to hang, then do

  cd `port dir coreutils`
  cd work/coreutils-6.9/lib
  sudo make CFLAGS= sha256.o sha512.o

then restart the failed port command. On second thought, I think it should be ok to run

  sudo port configure coreutils

and then follow the above procedure, but I haven't tried that to see if it really works.

[jmroot (Joshua Root)]

If you can upgrade to a newer version of XCode then you should do so. If that helps, then this is probably a gcc bug, and if that's the case, we probably can't do much about it.

[hanche]

It is most assuredly a gcc bug, and all you could do is to arrange for those few files to be compiled at a lower optimization setting. I see from my logs that I last rebuilt my coreutils on 2008-02-02. This time it went without a hitch. Leopard, XCode 3.0, gcc 4.0.1. I suspect this will continue to bite Tiger users on PPC, but obviously I am not in a position to test that, so I have nothing more to contribute on this ticket.

[elias@…]

assigning to maintainer.

[nox@…]

Is this fixed with coreutils 6.11?

[(none)]

Milestone Port Bugs deleted