objcopy sets wrong processor in IEEE-695-file (Repost)

[Luca Manai <luca dot manai at netit dot alcatel dot 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 ---

I exactly have the same problem.
I try to link 
 - an object produced by objcopy (from m68k-coff to ieee) with 
 - an ieee object produced by an HP cross compiler, 
using an HP cross linker.

The linker says that the Processor is set to "4" and abort the
linking...

Does anyone find a solution?
Should I modify the BFD for ieee? If yes, has anyone suggestions?

Thanks.
Bye.

Luca.
--
  Luca Manai       mailto:Luca.Manai@netit.alcatel.it

  ALCATEL Italia    -    Transmission System Division
  Via Trento, 30    -    20059 Vimercate (MI) - Italy
  Tel: (+39) 039 686.9181  -  Fax: (+39) 039 686.3590

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com