On 02/01/2012 06:54 AM, Andrew Haley wrote: > On 02/01/2012 12:37 PM, ~Stack~ wrote: >> On 02/01/2012 04:29 AM, Andrew Haley wrote: >>> On 02/01/2012 02:57 AM, ~Stack~ wrote: >>>> I have pasted the make error at the end of the email. I >>>> don't expect someone to solve our problems from it, but hopefully it >>>> helps to see part of the issue we have run into. >>> >>> You're using the wrong assembler. That's your system's >>> assembler program, not the 1750A assembler. You need to >>> run that gcc command with -v which will who you what gcc >>> is calling. You then need to make sure that the assembler >>> in gcc's path is the 1750A version. >> >> Thank you for the reply. >> >> I take it then that the assembler isn't provided with the gcc 3.1 >> download. I was hoping that the gcc tarball would be all inclusive. >> >> Any idea where I might be able to obtain a 1750 assembler then? > > In your Windows binary there must be an assembler. With that > assembler, if it is GNU, must be instructions where to get the > source code. So, what does that assembler say about -v or > -version? The same question applies to the linker. When I run the gcc command manually with the -v flag I get mostly the same output with the additional: gcc version 3.1.1 GNU CPP version 3.1.1 (cpplib) (MIL-STD-1750A) GNU C version 3.1.1 (1750a) compiled by GNU C version 2.96 20000731 (Red Hat Linux 7.2 2.96-129.7.2). So it doesn't look like it is linking against the assembler. To be honest, I was hoping it was a part of the download. :-) The download link where they found the Windows version is here: http://downloads.cleanscape.net/1750a/resources/cpp1750.zip I have not figured out which bits I need out of that download yet. Nor how to tell the build process to use the new linker. I do appreciate the help. I have never delved this deep into gcc before. Thanks! ~Stack~
Attachment:
signature.asc
Description: OpenPGP digital signature
