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] |
// // cross h8300 binutils-2.9.1 built by gcc-2.7.2 // $ ls -l h8300-hitachi-hms272/bin/h8300-hitachi-hms-ld -rwxr-xr-x 2 randall randall 1014908 Nov 12 14:58 h8300-hitachi-hms272/bin/h8300-hitachi-hms-ld // // cross h8300 binutils-2.9.1 built by // my build of native egcs-1.1 // $ ls -l h8300-hitachi-hms/bin/h8300-hitachi-hms-ld -rwxr-xr-x 2 randall randall 859579 Nov 10 06:39 h8300-hitachi-hms/bin/h8300-hitachi-hms-ld _both_ linkers core dump when trying to include an archive file either by -l<library> on linker command line, or by INPUT(<archive>.a) in the linker script. I tried two different archive files with the linkers, 1) libc.a, built from newlib-1.8.1 using the h8300 egcs-1.1 2) mon300l.a, built, presumably, by someone at hitachi using, I think, gcc 2.6.x on Solaris. I checked the mon300l.a archive itself using my h8300-hitachi-hms-ar and h8300-hitachi-hms-objdump and it looks ok. In fact, I'm presently working around the linker problem by linking to the extracted .o files rather than using the archive itself. So I'm pretty sure the problem's in the h8300 linker. It's looking like bug report time, but I'll try looking into what the linker's doing to see if I can find or at least narrow down the problem a bit more first. -- |\/| |/\| randall@elgar.com |\/| rsl@zanshinsys.com http://www.zanshinsys.com ________________________________________________ To get help for the crossgcc list, send mail to crossgcc-request@cygnus.com with the text 'help' (without the quotes) in the body of the message.