Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 64719 - circular-seeming, overly long build with nautilus-2.6.3-r1, using gcc-3.4.1 and glibc-
Summary: circular-seeming, overly long build with nautilus-2.6.3-r1, using gcc-3.4.1 a...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: Gentoo Toolchain Maintainers
Depends on:
Reported: 2004-09-19 23:29 UTC by Donnie Berkholz (RETIRED)
Modified: 2005-07-14 01:54 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

2070-nautilus-2.6.3-r1.log.bz2 (2070-nautilus-2.6.3-r1.log.bz2,47.78 KB, application/octet-stream)
2004-09-19 23:40 UTC, Donnie Berkholz (RETIRED)
emerge-info.txt (emerge-info.txt,2.21 KB, text/plain)
2004-09-19 23:41 UTC, Donnie Berkholz (RETIRED)
dmesg.txt (dmesg.txt,15.11 KB, text/plain)
2004-09-19 23:41 UTC, Donnie Berkholz (RETIRED)

Note You need to log in before you can comment on or make changes to this bug.
Description Donnie Berkholz (RETIRED) gentoo-dev 2004-09-19 23:29:52 UTC
donnie@supernova ~ $ splat nautilus
 * gnome-base/nautilus-2.6.3-r1

        Emerged at: Sun Sep 19 21:03:46 2004
        Build time: 2 hours, 9 minutes, and 43 seconds

This is a dual Athlon 2000 system. A build of the same on an Athlon 1800 (single) took less than 30 minutes.

I'm not sure whether this is a toolchain bug, gnome bug or neither.
Comment 1 Donnie Berkholz (RETIRED) gentoo-dev 2004-09-19 23:40:38 UTC
Created attachment 39991 [details]

Unfortunately the log was 13MB uncompressed, so I figured bzipping it down to
50KB would work out better.
Comment 2 Donnie Berkholz (RETIRED) gentoo-dev 2004-09-19 23:41:13 UTC
Created attachment 39992 [details]
Comment 3 Donnie Berkholz (RETIRED) gentoo-dev 2004-09-19 23:41:27 UTC
Created attachment 39993 [details]
Comment 4 foser (RETIRED) gentoo-dev 2004-09-20 04:34:28 UTC
well i guess this in the log explains the extra time it took :

make[1]: Warning: File `/usr/bin/orbit-idl-2' has modification time 6.8e+03 s in the future

i've never seen it before. I'd say your machine, guess something todo with SMP. That might be caused by toolchain bugs, they're doing crazy stuff there afaic.

I'm not sure what to do with this bug, i'd guess you are better of compiling -j1.
Comment 5 Donnie Berkholz (RETIRED) gentoo-dev 2004-09-20 08:53:25 UTC
I was also wondering whether the MCE notices in dmesg were related, but I don't know enough about Machine Check Exception to tell.

I'll give it another try with -j1 tonight, try to reproduce/not reproduce, etc.
Comment 6 Stephen Becker (RETIRED) gentoo-dev 2004-09-26 16:13:17 UTC
I ran into the same thing on mips building 2.6.3-r1 (o32 userland).  Switching MAKEOPTS to -j1 fixed this.  It seems like it has to be a toolchain bug, as I encountered something *very* similar with cc1plus running the cpu up to 100% indefinitely while building gcc 3.4.2-r2 with fortran support.  On that machine, the system compiler was/is 3.4.1-r2/3.4.2-r2.  Perhaps the toolchain herd should be added to this bug if it can be confirmed.  Donnie, could you try to build gcc-3.4.2-r2 with USE="f77" and MAKEOPTS set to -j2 and see if you can reproduce my problem there?
Comment 7 Stephen Becker (RETIRED) gentoo-dev 2004-09-26 16:15:13 UTC
I forgot to mention, the build machine is uniprocessor.
Comment 8 Joshua Kinard gentoo-dev 2004-09-26 16:32:28 UTC
fun fun happy happy toolchain oddities!

Anyone on toolchain got an idea w/ this?  I never hit geoman's reported fortran oddity on my O2, but then again, I used -j1 on that system.  
Comment 9 Jeremy Huddleston (RETIRED) gentoo-dev 2005-07-14 01:54:25 UTC
That modification time is 10 minutes in the future... I really doubt this is
toolchain related, and I can't trigger this bug... =/

I'm gonna close it cantfix unless someone really cares to delve into it...