This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: problem with parallel make
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Andreas Jaeger <aj at suse dot de>
- Cc: Josef Zlomek <zlomj9am at artax dot karlin dot mff dot cuni dot cz>, gcc at gcc dot gnu dot org,gcc-bugs at gcc dot gnu dot org
- Date: Sun, 19 Oct 2003 22:07:29 -0400
- Subject: Re: problem with parallel make
- References: <holls6h1yr.fsf@byrd.suse.de> <20031018122717.GA11645@artax.karlin.mff.cuni.cz> <u88yni39r6.fsf@gromit.moeb>
On Sat, Oct 18, 2003 at 04:23:25PM +0200, Andreas Jaeger wrote:
> Josef Zlomek <zlomj9am@artax.karlin.mff.cuni.cz> writes:
>
> >> building with multilibs on x86_64-linux-gnu I get a build failure with
> >> a parallel make (-j2 -l7) on my dual Opteron system:
> >> /usr/bin/ld: warning: i386 architecture of input file `.libs/allchblk.o' is incompatible with
> >> i386:x86-64 output
> >
> > The bug only apperas when -j2 is used, with -j4 it is gone. I expect when more
> > processes are used something gets build soon enough.
> >
> > Following patch caused or exposed it.
> >
> > 2003-08-27 Daniel Jacobowitz <drow@mvista.com>
> >
> > * configure.in: Set RAW_CXX_FOR_TARGET if unset.
> > * configure: Regenerated.
> >
> > Josef
>
> Thanks for tracking this down. Daniel and Nathanael, do you have any
> ideas on how to fix this?
It must be an exposed rather than created... RAW_CXX_FOR_TARGET used to
be left unset, which would cause build failures in my environment. I
can't see how this could cause -m32 to disappear, especially not from
CC.
>
> Cheers,
> Andreas
>
> >> The problem is that -m32 is not passed to GCC. If I run a sequential
> >> build, this works for me, just the parallel one fails on this machine
> >> (it works on another where I tested it).
> >>
> >> Looking at x86_64-suse-linux-gnu/32/config.cache I noticed:
> >>
> >> ac_cv_prog_CC=${ac_cv_prog_CC='/builds/gcc/misc/gcc/xgcc -B/builds/gcc/misc/gcc/
> >> -B/opt/gcc/3.4-devel/x86_64-suse-linux-gnu/bin/ -B/opt/gcc/3.4-devel/x86_64-sus
> >> e-linux-gnu/lib/ -isystem /opt/gcc/3.4-devel/x86_64-suse-linux-gnu/include -isys
> >> tem /opt/gcc/3.4-devel/x86_64-suse-linux-gnu/sys-include'}
> >> ac_cv_prog_CPP=${ac_cv_prog_CPP='/builds/gcc/misc/gcc/xgcc -B/builds/gcc/misc/gc
> >> c/ -B/opt/gcc/3.4-devel/x86_64-suse-linux-gnu/bin/ -B/opt/gcc/3.4-devel/x86_64-s
> >> use-linux-gnu/lib/ -isystem /opt/gcc/3.4-devel/x86_64-suse-linux-gnu/include -is
> >> ystem /opt/gcc/3.4-devel/x86_64-suse-linux-gnu/sys-include -E'}
> >>
> >> So, the -m32 is missing. But it's there for CXXCPP:
> >> ac_cv_prog_CXXCPP=${ac_cv_prog_CXXCPP='/builds/gcc/misc/gcc/xgcc -shared-libgcc
> >> -B/builds/gcc/misc/gcc/ -nostdinc++ -L/builds/gcc/misc/x86_64-suse-linux-gnu/32/
> >> libstdc++-v3/src -L/builds/gcc/misc/x86_64-suse-linux-gnu/32/libstdc++-v3/src/.l
> >> ibs -B/opt/gcc/3.4-devel/x86_64-suse-linux-gnu/bin/ -B/opt/gcc/3.4-devel/x86_64-
> >> suse-linux-gnu/lib/ -isystem /opt/gcc/3.4-devel/x86_64-suse-linux-gnu/include -i
> >> system /opt/gcc/3.4-devel/x86_64-suse-linux-gnu/sys-include -m32 -E'}
> >
> >
>
> Andreas
> --
> Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
> SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany
> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer