as vs. m68k-rtems-as!
Scott Newell
newell at cei.net
Mon Apr 29 02:53:48 UTC 2002
Just getting started, so I may have done everything out of order. I've got
cygwin installed, and I've grabbed the prebuilt cygwin binaries (tarred and
gzipped). Finally got m68k-rtems-gcc installed in the right place, and it
seems to be picking up the correct spec file. However...it's still trying
to run the native cygwin as.exe instead of m68k-rtems-as.exe! (I've also
got the i386-rtems cross compiler installed--same problem with it.)
The online library page (4.3.1) mentions three possibilities:
Binutils patch not applied correctly
Binutils not built
Current directory is in your path
Well, I didn't build binutils, but they're part of the cygwin download.
I've double checked, and the current directory is _not_ in my path. What
else should I check?
My path echos back as: /usr/local/bin:/usr/bin:/opt/rtems/bin
m68k-rtems-gcc -v f.c gives me:
Reading specs from /opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2/specs
gcc version 2.95.2 19991024 (release)
/opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2/cpp.exe -lang-c -v -iprefix
m68k-rtems/2.95.2/ -D__GNUC__=2 -D__GNUC_MINOR__=95 -Dmc68000 -Drtems
-D__rtems__ -D__ELF__ -D__mc68000__ -D__rtems__ -D__rtems__ -D__ELF__
-D__mc68000 -D__rtems -Asystem(rtems) -Acpu(mc68000) -Acpu(m68k) -Ama
hine(m68k) -D__HAVE_68881__ -Dmc68020 -D__mc68020 -D__mc68020__ f.c
/tmp/ccmaXRBX.i
GNU CPP version 2.95.2 19991024 (release) (68k, Motorola syntax)
#include "..." search starts here:
#include <...> search starts here:
/opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2/include
/opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2/../../../../m68k-rtems/include
End of search list.
The following default directories have been omitted from the search path:
/opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2/../../../../include/g++-3
/opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2/../../../../m68k-rtems/sys-include
End of omitted list.
/opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2/cc1.exe /tmp/ccmaXRBX.i -quiet
-dumpbase f.c -version -o /tmp/cca0Cb3T.s
GNU C version 2.95.2 19991024 (release) (m68k-rtems) compiled by GNU C
version 2.95.2 19991024 (release).
as -mc68020 -o /tmp/ccOOcr6R.o /tmp/cca0Cb3T.s
as: unrecognized option `-mc68020'
And finally,
m68k-rtems-gcc --print-search-dirs spits out:
install: /opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2/
programs:
m68k-rtems/2.95.2/::/opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2/:/opt/rtems/lib
/gcc-lib/m68k-rtems/:/usr/lib/gcc/m68k-rtems/2.95.2/:/
usr/lib/gcc/m68k-rtems/:/opt/rtems/m68k-rtems/bin/m68k-rtems/2.95.2/:/opt/rt
ems/m68k-rtems/bin/
libraries:
m68k-rtems/2.95.2/::/opt/rtems/lib/gcc-lib/m68k-rtems/2.95.2/:/usr/lib/gcc/m
68k-rtems/2.95.2/:/opt/rtems/m68k-rtems/lib/m68k-rtem
s/2.95.2/:/opt/rtems/m68k-rtems/lib/
It looks like it should be able to find m68k-rtems-as.exe, as it's even in
the path. I don't understand why it's running as.exe, instead of
m68k-rtems-as.exe.
thanks,
newell
More information about the users
mailing list