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] |
jack albert wrote:How come I can still specify -m68030 on my i386 system? I would expect compilation to fail, but it doesn't. Did it really compile for the i386 processor or the m68k? (I can't tell since it's supposed to run on the m68k - but I have other problems so I can't run it just yet). My confusion is the fact that it *looks* like I can compile for the m68k processor on my default gcc installation (Suse 9.1).
This doesn't sound possible, my SuSE 9.2 one gave :
kai@Dell:/data1/home/kai-old/test/hello> gcc -v
Reading specs from /usr/lib/gcc-lib/i586-suse-linux/3.3.4/specs
<snip>
gcc version 3.3.4 (pre 3.3.5 20040809)
kai@Dell:/data1/home/kai-old/test/hello> gcc -m68030 -o hello_m68k hello.c
cc1: error: invalid option `68030'
and your 9.1 one GCC should behave identically... Only a real m68k targeted
GCC understands that '-m68030' option.
After using that '-b' to tell the "target", the native SuSE 9.2 'gcc' gave :I also do not understand the -b option from the gcc man page. How does gcc know to use a different gcc compiler installed somewhere else.
This is probably some ancient option from the age when even 50-100 kbytes more
for a separate 'gcc', 'g++' etc. drivers was "too much disk consuming"....
Using a common driver for many GCCs doesn't sound sane in any way nowadays, not evenwas expressed as :
for just the same target...
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |