[lfs-support] Final GCC Compile Weirdness - 1 Time? No, 2 nd Time? Perfect!

Andrew Benton b3nton at gmail.com
Tue Jan 10 02:50:02 PST 2012

On Tue, 10 Jan 2012 09:21:01 +0000
Firerat <firer4t at googlemail.com> wrote:

> I find that if a make fails first time, but completes (or gets further ) on
> second run it is due to some race condition where you have multiple jobs
> and a new job thread is dependent on something that hasn't completed.
> The simplest way around this is to flag the make with -j1

FWIW I've never had a problem compiling gcc with make -j4
Also, if you read his script he doesn't use multiple jobs when he runs:
make -k check

> If you are having trouble with slow builds then have a look at top on your
> host system and see if anything is eating CPU and/or memory.
> I have had problems with polkitd and nautilus on Ubuntu (bad pulseaudio
> setup)
> Chrome is also a mem/CPU hog, especially if flash is enabled

Are you compiling in a virtual machine? If so, perhaps it is not making
all the system's resources available?


More information about the lfs-support mailing list