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....
Date: Tue, 05 Jan 1999 05:40:00 -0000 [thread overview]
Message-ID: <199901051340.IAA01663@subrogation.cygnus.com> (raw)
In-Reply-To: <199901051117.QAA11458@bombay.ddeorg.soft.net>
Date: Tue, 05 Jan 1999 16:47:04 +0530
From: "Koundinya.K" <kk@ddeorg.soft.net>
I have been using the egcs-2.91.57 19980901 (egcs-1.1 release) gcc and g++
compilers and all the other tools on my system which is MIPS (R4000) based
running the SVR4.2 UNIX on the Supermax Business Server for a few months now
and they seem to work fine.
How ever I am still not able to use the GNU linker. For making the egcs
port I used the native linker ( from the EPC - Edinberg portable compiler
and Tools) and it took me 6 months !!. I am not able to generate the dynamic
libraries. The GNU assembler (gas) and the native ld pair does not seem to
work.
The GNU linker does not fully support shared libraries on MIPS ELF
platforms. It seems to work well enough for MIPS GNU/Linux; I don't
know the details, and I don't know if all the patches have been
integrated into the mainline sources. Somebody is working on
improving the Irix 6 support, which will hopefully include
improvements for the general MIPS ELF support.
I don't know why gas does not work with the native linker. That does
work on Irix. It isn't likely to work if you configure gas for
mips-sysv, as that appears to generate ECOFF. Make sure you configure
for mips-elf or mips-linux-gnu, or fix the gas/configure.in file and
regenerate gas/configure.
--------------- Output of test --------------------------------------------
../test
Hello World
dynamic linker: ./test: unidentifiable procedure reference (address =
0x40062cd8)
Killed
-----------------------------------------------------------------------------
-
I tried to use the readelf utility , but got no clues.
Try changing the definition of SGI_COMPAT in bfd/elf32-mips.c from 1
to 0. By default the linker will generate some form of the Irix
quickstart relocs. However, you should expect to run into other
problems, particularly if you try to generate shared libraries
yourself.
Ian
next prev parent reply other threads:[~1999-01-05 5:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-05 3:16 Koundinya.K
1999-01-05 5:40 ` Ian Lance Taylor [this message]
1999-01-09 16:31 ` ralf
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=199901051340.IAA01663@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).