This is the mail archive of the crossgcc@cygnus.com mailing list for the crossgcc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
As far as I can tell, ieee support in the gnu tools works well enough to be able to read most ieee files created by other vendors' tools, but not well enough to be able to create all the different variations that are in use. The best solution seems to be to use some other file format. (Distant) Second-best would be to hack the bfd sources to get IEEE the way you want it. Scott Jepsen Hans Peter wrote: > > Hi > > We are using objcopy ver. 2.9.1 to generate an ieee-695 file from a coff > file. > > The commandline is: > > objcopy --debugging --output-target=ieee mainprog.cof mainprog.x > > In the ieee-695 file the Processor is set to "4" and not "68020" as expected > - or better "68331". This makes our debugger reject the code. > > objdump says that the file format of the coff file is coff-m68k. > > Is this a bug or are we doing something wrong? > > Kind regards > > Hans Peter > > -- > Hans Peter Jepsen Phone: +45 74 88 50 11 > Danfoss Drives A/S, Fax: +45 74 65 28 38 > DG-257, Ulsnaes 1, Email: Hans_Peter_Jepsen@danfoss.com > DK-6300 Graasten, Denmark http://www.danfoss.com/drives > --- This message was transmitted on 100% recycled electrons --- > > _______________________________________________ > New CrossGCC FAQ: http://www.objsw.com/CrossGCC > _______________________________________________ > To remove yourself from the crossgcc list, send > mail to crossgcc-request@cygnus.com with the > text 'unsubscribe' (without the quotes) in the > body of the message. _______________________________________________ New CrossGCC FAQ: http://www.objsw.com/CrossGCC _______________________________________________ To remove yourself from the crossgcc list, send mail to crossgcc-request@cygnus.com with the text 'unsubscribe' (without the quotes) in the body of the message.