Re: Compiling GCC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Paulo J. Matos writes:
 > On 1/31/07, Andrew Haley <aph@xxxxxxxxxx> wrote:
 > > Paulo J. Matos writes:
 > >  > Hello all,
 > >  >
 > >  > I'm trying to compile gcc in my home dir, just to make some tests but
 > >  > I've having some errors during compilation. Compilation is being
 > >  > performed in an intel duo core. This is what I do:
 > >  > ~/ tar -xvjf gcc-4.1.1.tar.bz2
 > >  > ~/ mkdir gcc-build
 > >  > ~/ cd gcc-build
 > >  > ~/ ../gcc-4.1.1/configure --prefix=/home/pmatos/gcc-bin
 > >  > --program-prefix=dr- --with-gnu-as --with-as=/usr/bin/as --with-gnu-ld
 > >  > --with-ld=/usr/bin/ld --host=x86_64-pc-linux-gnu
 > >  > --build=x86_64-pc-linux-gnu --disable-altivec --enable-nls
 > >  > --without-included-gettext --with-system-zlib --disable-checking
 > >  > --disable-werror --enable-secureplt --disable-libunwind-exceptions
 > >  > --enable-multilib --disable-libmudflap --disable-libssp
 > >  > --disable-libgcj --enable-shared --enable-threads=posix
 > >  > --enable-__cxa_atexit --enable-clocale=gnu
 > >  > (Note: some of these flags were copied from the Gentoo build, since I
 > >  > really didn't know what to use, the dr- prefix is just something so
 > >  > that the final binary doesn't shadow my production gcc)
 > >
 > > The build system thinks you're building a cross-compiler.  This is bad.
 > >
 > 
 > Why do you say that? Why do you say that the system thinks I'm
 > building a crosscompiler?
 > Probably this is due to the fact that in Gentoo intel core duo follow
 > the amd64 branch, since they are 64 bit processors...
 > 
 > > You need to get rid of some of the configure arguments.
 > >
 > >  ~/ ../gcc-4.1.1/configure --prefix=/home/pmatos/gcc-bin
 > >  --disable-altivec --enable-nls
 > >  --without-included-gettext --with-system-zlib
 > >  --disable-werror --enable-secureplt --disable-libunwind-exceptions
 > >  --enable-multilib --disable-libmudflap --disable-libssp
 > >  --disable-libgcj --enable-shared --enable-threads=posix
 > >  --enable-__cxa_atexit --enable-clocale=gnu
 > >
 > > ought to do it.
 > >
 > 
 > Exactly the same error:
 > checking for x86_64-unknown-linux-gnu-gcc...
 > /home/pmatos/gcc411-build/./gcc/xgcc
 > -B/home/pmatos/gcc411-build/./gcc/
 > -B/home/pmatos/gcc-bin/x86_64-unknown-linux-gnu/bin/
 > -B/home/pmatos/gcc-bin/x86_64-unknown-linux-gnu/lib/ -isystem
 > /home/pmatos/gcc-bin/x86_64-unknown-linux-gnu/include -isystem
 > /home/pmatos/gcc-bin/x86_64-unknown-linux-gnu/sys-include  -m32
 > checking for C compiler default output file name... a.out
 > checking whether the C compiler works... configure: error: cannot run
 > C compiled programs.

The problem might be that you don't have the target libs installed for
a multilib build.  Try --disable-multilib.

Andrew.

[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux