Mail Archives: djgpp/1994/08/25/22:15:25
I'm on a sparc, trying to build a cross sytem to support
386 development (djgcc, netbsd, freebsd, linux)
I have a cross-compile working, a cross-assembler which works,
and objdump works...
When I do objdump --info I get:
a.outt-sunos-big
(header big endian, data big endian)
sparc
a.out-i386-bsd
(header little endian, data little endian)
sparc
i386
a.out-netbsd-386
(header little endian, data little endian)
sparc
i386
coff-i386
(header little endian, data little endian)
i386
coff-sparc-lynx
(header big endian, data big endian)
sparc
a.out-sparc-lynx
(header big endian, data big endian)
sparc
srec
(header big endian, data big endian)
sparc
i386
symbolsrec
(header big endian, data big endian)
sparc
i386
a.out-sunos-big a.out-i386-bsd a.out-netbsd-386 coff-i386 coff-sparc-lynx
sparc a.out-sunos-big a.out-i386-bsd a.out-netbsd-386 --------- coff-sparc-lynx
i386 --------------- a.out-i386-bsd a.out-netbsd-386 coff-i386 ---------------
a.out-sparc-lynx srec symbolsrec
sparc a.out-sparc-lynx srec symbolsrec
i386 ---------------- srec symbolsrec
Which looks reasonable...
But I can't cross-link...
I've done permutations on
GNUTARGET=default
GNUTARGET=coff-i386
and all types of other incantations...
I consistently get:
leisner AT gasface$ gnu-ld -v foo.o
ld version 2.4 (with BFD 2.4)
gnu-ld: warning: i386 architecture of input file `foo.o' is incompatible with sparc output
gnu-ld:a.out: can't set architecture: File in wrong format
Is there a way to do an ld --info (link objdump --info)
Advice?
marty
Member of the League of Programming Freedom
leisner AT sdsp DOT mc DOT xerox DOT com leisner AT eso DOT mc DOT xerox DOT com
- Raw text -