Re: cross-compiling on 64 to 32-bit Linuxlocalhost/

2010-03-03 Thread Grégory Pakosz
> You don't need to specify -m32 if you have a tool set prefixed with the > cross tag. The reason for using -m32 is because the user wants to use his > 64-bit gcc to compile 32-bit code, so he has to tell the compiler to switch > to 32-bit mode also. (Incidentally, if you're running on Linux, might

Re: cross-compiling on 64 to 32-bit Linuxlocalhost/

2010-03-02 Thread John Calcote
Hi Gregory, On 3/2/2010 4:14 PM, Grégory Pakosz wrote: ./configure --host=i686-pc-linux-gnu \ --prefix=/arch/x86-linux/gnu \ CC="gcc -m32 -march=i586" \ CXX="g++ -m32 -march=i586" \ LDFLAGS="-m32" I'm curious about why setting

Re: cross-compiling on 64 to 32-bit Linuxlocalhost/

2010-03-02 Thread Grégory Pakosz
> You need a bi-arch system, that is, one that has the system libraries both in > a > 64-bit variant and in a 32-bit variant (typically in /lib64 and /lib, > respectively). > For compiling in 32-bit mode, I use > ./configure --host=i686-pc-linux-gnu \ > --prefix=/arch/x86-linux/gn