This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Building mainline and 4.2 on Debian/amd64
- From: Matthias Klose <doko at cs dot tu-berlin dot de>
- To: Florian Weimer <fw at deneb dot enyo dot de>
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 19 Mar 2007 22:43:37 +0100
- Subject: Re: Building mainline and 4.2 on Debian/amd64
- References: <87ircyjxcm.fsf@mid.deneb.enyo.de>
Florian Weimer writes:
> Is there a convenient switch to make GCC bootstrap on Debian/amd64
> without patching the build infrastructure? Apparently, GCC tries to
> build 32-bit variants of all libraries (using -m32), but the new
> compiler uses the 64-bit libc instead of the 32-bit libc, hence
> building them fails.
>
> I don't need the 32-bit libraries, so disabling their compilation
> would be fine. --enable-targets at configure time might do the trick,
> but I don't know what arguments are accepted.
Others already mentioned --disable-multilib.
If you do want to build a multilib build, make sure that the
libc6-dev-i386 package is installed, and the appended patch is applied
(Maybe a patch using some Makefile conditionals could be applied
upstream). For historical reasons lib64 is a symlink to lib, and the
32bit libs are installed into lib32. Building the java gtk/x peers
doesn't work, because the gtk/gnome libs are not available for 32bit.
Matthias
--- gcc/config/i386/t-linux64~ 2002-11-28 14:47:02.000000000 +0000
+++ gcc/config/i386/t-linux64 2004-06-02 16:07:30.533131301 +0000
@@ -6,7 +6,7 @@
MULTILIB_OPTIONS = m64/m32
MULTILIB_DIRNAMES = 64 32
-MULTILIB_OSDIRNAMES = ../lib64 ../lib
+MULTILIB_OSDIRNAMES = ../lib ../lib32
LIBGCC = stmp-multilib
INSTALL_LIBGCC = install-multilib