This is the mail archive of the gcc@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] | |
Daniel Jacobowitz <drow@mvista.com> writes: > > ../configure --enable-checking --enable-languages=c,c++,objc,f77 > > make -j2 bootstrap > Then, if CC needs -m64 in order to emit 64-bit code, how is 32-bit code > being built or -m64 being specified? There's something you're not > telling me :) This is a bi-arch compiler: - 64-bit code is generated by default, so no need for -m64. - -m32 is needed for 32-bit code and enabled by default. It's really just those two commands. GCC is clever enough to add -m32 itself for x86_64 (see config/i386/t-linux64) Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Attachment:
pgp00000.pgp
Description: PGP signature
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |