This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: problem with parallel make
> > 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.
Yes, that will be the reason.
> You mean libf2c,
> though, don't you?
Yes.
> In any case, please post the configure and make commands you are using,
> including any environment variables.
../configure --enable-checking --enable-languages=c,c++,objc,f77
make -j2 bootstrap
Josef