This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: problem with parallel make
On Mon, Oct 20, 2003 at 09:00:55PM +0200, Josef Zlomek wrote:
> > > >> 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.
>
> I'm sorry I identified the wrong patch.
> According to binary search it should be this patch from libiberty/:
>
> 2003-08-27 Daniel Jacobowitz <drow@mvista.com>
>
> * aclocal.m4: Include acx.m4 and no-executables.m4.
> (libiberty_AC_FUNC_STRNCMP): Use AC_LIBOBJ.
> (LIB_AC_PROG_CC): Remove.
> * configure.in: Update AC_PREREQ to 2.57. Use GCC_NO_EXECUTABLES.
> Use AC_PROG_CC and set ac_libiberty_warn_cflags instead of using
> LIB_AC_PROG_CC. Use AC_LIBOBJ. Call AC_ISC_POSIX later, only if
> performing link tests.
> * configure: Regenerated.
>
> I am wondering how libiberty change could affect build failure in libffi:
>
> /usr/bin/ld: warning: i386 architecture of input file `libE77/.libs/Lsystem.o' is incompatible with i386:x86-64 output
> /usr/bin/ld: warning: i386 architecture of input file `libE77/.libs/Lflush.o' is incompatible with i386:x86-64 output
> /usr/bin/ld: warning: i386 architecture of input file `libE77/.libs/Lftell.o' is incompatible with i386:x86-64 output
> /usr/bin/ld: warning: i386 architecture of input file `libE77/.libs/Lfseek.o' is incompatible with i386:x86-64 output
> /usr/bin/ld: warning: i386 architecture of input file `libE77/.libs/Laccess.o' is incompatible with i386:x86-64 output
> /usr/bin/ld: warning: i386 architecture of input file `libE77/.libs/Lbesj0.o' is incompatible with i386:x86-64 output
This is more believable. The problem is probably caused by the config.cache
shared by libiberty and libffi; if autoconf 2.57 is putting the wrong
thing there, we'll fall apart later in libffi. You mean libf2c,
though, don't you?
In any case, please post the configure and make commands you are using,
including any environment variables.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer