long running gcc process when building world
leafy7382 at gmail.com
Mon Jan 14 18:46:23 PST 2008
On Jan 15, 2008 9:06 AM, Kris Kennaway <kris at freebsd.org> wrote:
> Jiawei Ye wrote:
> > Having updated to -current as of Jan 14, gcc now drops in to
> > compilation when building world:
> > cc -O2 -fno-strict-aliasing -pipe -DIN_GCC -DHAVE_CONFIG_H
> > -DPREFIX=\"/usr/obj/usr/src/tmp/usr\"
> > -I/tmp/obj/usr/src/tmp/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools
> > -I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools
> > -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc
> > -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config
> > -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/include
> > -I/usr/obj/usr/src/tmp/legacy/usr/include -c ../cc_tools/insn-attrtab.c
> > This has been running for more than 5 minutes as of now. The same
> > occurs when building java/jdk16.
> 5 minutes != infinity. This seems reasonable to me, it's a 3.5MB
> machine-generated C file. Turn down the optimization level if you can't
> bear to wait that long for it :)
> Ok, restarted the build job and it took 8:45 wall time to finish compiling
the file. I brought this up because I saw another long-running compilation
when trying to build java/jdk16 (1.5hr on a single file). It did not take
this long before updating to the latest current. Sorry for the noise.
"If it looks like a duck, walks like a duck, and quacks like a duck, then to
the end user it's a duck, and end users have made it pretty clear they want
a duck; whether the duck drinks hot chocolate or coffee is irrelevant."
More information about the freebsd-current