RE: Spam:**********, Re: objcopy problems

I installed the elf toolchain from codesourcery, it went on easily enough
and after sorting out PATH environments it works fine alongside our original
gnu install. I can use both toolchains independently.

But the elf-objcopy doesn't work when used with our coff-build (although it
doesn't crash)

C:\Games\heber\demo>m68k-elf-objcopy --debugging -O ieee -R .id -R .system
demo.cof demo.iee
demo.cof: .stab: stab entry 1 is corrupt, strx = 0xd3000000, type = 8
demo.cof: .stab: stab entry 3 is corrupt, strx = 0x0, type = 37
demo.cof: .stab: stab entry 4 is corrupt, strx = 0x0, type = 84
demo.cof: .stab: stab entry 5 is corrupt, strx = 0x0, type = 110
demo.cof: .stab: stab entry 6 is corrupt, strx = 0x0, type = 162
demo.cof: .stab: stab entry 7 is corrupt, strx = 0x0, type = 218
demo.cof: .stab: stab entry 8 is corrupt, strx = 0x1, type = 23

---------------------------

So it looks like I cant mix toolchain tools. (mix coff compilers and elf
objcopy)

I've tried a full rebuild with the new ELF toolchain but get architecture
problems with our libraries at ld stage.
The example below is a single example, every .o file in our library (3rd
party, no src) produces this error.

m68k-elf-ld: m68k:68020 architecture of input file
`/heber/pluto6/libs/gnu/pluto6\libdbug.a(dbug-outbyte.o)' is incompatible
with m68k:isa-a:nodiv output

--------------------

So It looks like my libraries are compiled as 68020 (and I cant change that)
And the codesourcery tools are hardcoded to  isa-a (coldfire) 

Is there an old coff-objcopy out there I could use? I don't have the means
to rebuild it though. My version is 2.9.1 (1997)



Thanks
Jaysen




-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Chris Johns
Sent: 09 August 2008 04:08
To: Jaysen Roper
Subject: Spam:**********, Re: [ColdFire] objcopy problems

X-SpamDetect-Info: ------------- Start ASpam results ---------------
X-SpamDetect-Info: This message may be spam. This message BODY has been
altered to show you the spam information 
X-SpamDetect: **********: 10.400001 From3consonants=0.3, Share Market
Scam=2.0, SPF Soft=3.0, DodgySource=2.0, SPF Default Fail=2.5, X-Verify-SMTP
present=0.6
X-SpamDetect-Info: ------------- End ASpam results -----------------

Jaysen Roper wrote:
> I am having problems with m68k-coff-objcopy.exe
> 
> Whenever I enable "-debugging" it crashes with the following error.
> 
> m68k-coff-objcopy --debugging -O ieee -R .id -R .system demo.bin demo.695
> [main] C:\heber\exe\gcc-m68k\bin\m68k-coff-objcopy.exe 1030 (0) 
> handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
> [main] m68k-coff-objcopy 1030 (0) handle_exceptions: Dumping stack trace 
> to m68k-coff-objcopy.exe.core
> make: *** [demo.695] Error 11
> 
> I am using David Fiddes excellent GCC-M68K v6 (1998) with no other nix 
> tools in the mix.
> 
> Davids tools are based on EGCS-1.1.2 and GNU Binutils-2.9.1
> 
> I have pulled 5 projects out of our archive, and sure enough, this 
> happens on all builds (none of them had -debugging enabled)
> 
> I have tried objcopy with ieee / srec / tekhex / ihex / binary. All give 
> the same error at the same point.
> 
> Ieee is our preferred format because it is the preferred format of our 
> new IDE/DBG system.
> 
> Is there a reliable way of converting our coff files to ieee?
> 

The coff format is not used that much these days with the m68k target. I
think 
all are ELF.

I suggest you take a look at the Codesourcery tools available for download 
from their web site. Install those tools and see how the objcopy in their 
package goes. It may not crash.

Regards
Chris
---
[email protected]              Send a post to the list.
[email protected]        Join the list.
[email protected]    Join the list in digest mode.
[email protected]     Leave the list.



---
[email protected]              Send a post to the list.
[email protected]        Join the list.
[email protected]    Join the list in digest mode.
[email protected]     Leave the list.