From: Ian Lance Taylor <ian@cygnus.com>
To: kk@ddeorg.soft.net
Cc: gas2@cygnus.com, bfd@cygnus.com
Subject: Re: Problems with the GNU linker on mips...
Date: Sat, 30 Jan 1999 09:36:00 -0000 [thread overview]
Message-ID: <199901301736.MAA19237@subrogation.cygnus.com> (raw)
In-Reply-To: <199901301059.QAA11917@bombay.ddeorg.soft.net>
Date: Sat, 30 Jan 1999 16:29:54 +0530
From: "Koundinya.K" <kk@ddeorg.soft.net>
I applied this change and generated the new linker, and as usual I tried to
run the test program . The linking gave me the following message ...
------------- Clip of the compile log of gcc -v t.c -o tt1
-------------------
/usr/local/mips-dde-sysv4.2MP/bin/ld -V -Qy -o tt1 /lib/crt1.o /lib/crti.o
/lib/values-Xa.o -L/usr/local/lib/gcc-lib/mips-dde-sysv4.2MP/egcs-2.91.57
-L/usr/local/mips-dde-sysv4.2MP/lib -L/usr/local/lib /var/tmp/ccjlVzGK.o
-lgcc -L/usr/lib -lc -lgcc /lib/crtn.o
GNU ld version 2.9.4 (with BFD 990118)
Supported emulations:
elf32bsmip
/usr/local/mips-dde-sysv4.2MP/bin/ld: bfd assertion fail
.../../gas-990118/bfd/elf32-mips.c:5750
Which assertion is that? There is no assertion on line 5750 of the
elf32-mips.cfile here, probably because of the patches you have
applied. Looking at the code there may help you figure out the
problem. Or it may be unimportant.
-------------------------------Ends here ------------------------------------
and when I try to run
../tt1
ld.so: ./tt1: relocation error: symbol not found: __rld_map
Killed
I am not able to trace out this. Any pointers / hints to get out of this
problem will be helpful.
Search for "__rld_map" in elf32-mips.c. Some of the associated code
is SGI_COMPAT, and some is not. Probably, it all should be.
You are probably going to have to do some debugging and programming to
get this code to work for you.
Ian
prev parent reply other threads:[~1999-01-30 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-30 2:59 Koundinya.K
1999-01-30 9:36 ` Ian Lance Taylor [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199901301736.MAA19237@subrogation.cygnus.com \
--to=ian@cygnus.com \
--cc=bfd@cygnus.com \
--cc=gas2@cygnus.com \
--cc=kk@ddeorg.soft.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).