This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Brian Dessent wrote:
Brian Rose wrote:
Note: I am an embedded developer who has spent the better part of 10 years
doing VxWorks and a little WinCE. So feel free to get technical. Its just
that I am relatively inexperienced with open source software on the Cygwin
platform and I am not used to having to build my own tools.
Try running the failing gcc command with -v to see what it's doing. Is it calling the correct 'as'?
I added a -v to the FLAGS_FOR_TARGET and I see the following line before the error now,
/home/brose/rtems/tools/m68k-elf/bin/as.exe -m68040 -o libgcc/m68040/_fixunsdfsi.o /cygdrive/c/DOCUME~1/brose/LOCALS~1/Temp/ccghXdpv.s
So it looks like the correct assembler is being called. But then I do 'as --version' and I see that "This assembler has been configured for a target of 'i686-pc-cygwin'. So it looks like when I built my binutils, it made the incorrect as.
How do I point GCC to the correct as? I'm guessing there is a configure option?
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |