This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Default 32 bit output


2007/1/1, Kai Ruottu <karuottu@mbnet.fi>:

 But maybe the configury system could be misleaded (as people so easily
are :-), so
lying badly enough could help !  ("The bigger the lie the easier it is
to believe!") What
about configuring using :

 CC=gcc  \
 CFLAGS=-m32  \
 ../configure --prefix=/storage/GCC-32-i686/opt --disable-nls \
 --enable-languages=c,c++ \
 --build=i686-linux-gnu --host=i686-linux-gnu --target=i686-linux-gnu

ie telling that you are building on a Linux/i686, the becoming host is
also this and the
target system too...  So this lie should force a totally "normal" 32-bit
GCC for a 32-bit
Linux being produced...  BUT:  Unfortunately this kind of GCC produces
ONLY 32-bit
apps, there is no '-m64' possibility in it!  Or at least has not been
this far :-(

This is ok since I don't need 64 bit output. Unfortunately by using this flags I still get errors :-( Could you please tell me what flags I should use with binutils in this case. Maby I'm making something wrong there.

Thanks.

r. Domen


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]