This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
AW: building gcc to support -mx32
- From: "Warlich, Christof" <christof dot warlich at siemens dot com>
- To: "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
- Date: Tue, 15 Apr 2014 06:39:11 +0000
- Subject: AW: building gcc to support -mx32
- Authentication-results: sourceware.org; auth=none
Ping ....
As I got no response: Is x32 support a somewhat unusual configuration for x86_64?
-----Ursprüngliche Nachricht-----
Von: Warlich, Christof
Gesendet: Mittwoch, 9. April 2014 10:42
An: gcc-help@gcc.gnu.org
Betreff: building gcc to support -mx32
Hi,
while I can (cross-)compile an x86_64-mygcc-linux-gnu GCC to support both -m32 and -m64 on a x86_64-unknown-linux-gnu host, I'm stuck when adding support for -mx32.
I'm doing a sysroot build, with the sysroot directory initially populated with the appropriate glibc files in the directories lib, lib64 and libx32 for 32, 64 and x32 glibc.
Unfortunately, the build fails when linking x32/libgcc_s.so.1.tmp, because it tries to link against the libc found in $sysroot/lib instead of using the one in $sysroot/libx32.
Can anyone tell how to best resolve this? I can't move the files from $sysroot/libx32 to $sysroot/lib because this would break the build for -m32.
Thanks for any help,
Chris
P.S.: For completeness, this is my GCC configure:
sourcedir/configure' --target=x86_64-mygcc-linux-gnu --prefix=~/toolchain --with-sysroot=~/toolchain/x86_64-audis4-linux-gnueabi/sysroot --with-build-sysroot=$sysroot --enable-languages=c,c++ --with-multilib-list=m32,m64,mx32 --enable-multiarch
Everything works fine when removing mx32 from the multilib-list.