From: Lee Iverson <leei@ai.sri.com>
To: egcs@cygnus.com
Subject: Problems building shared libraries under Irix6
Date: Tue, 16 Dec 1997 10:08:00 -0000 [thread overview]
Message-ID: <199712161724.JAA25082@Canada.AI.SRI.COM> (raw)
All of the discussion wrt. __register_frame under Linux (mostly on
gcc2 with spillover here) begs an important question: why is libgcc.a
linked in when building shared libraries? Under Irix 6.x, this
inclusion on the link line seems to break shared libraries
completely. They can no longer be linked against since
__register_frame was included.
If libgcc was a properly versioned shared library, however, things
might actually work. For now, I'm experimenting with adding the
following lines to specs (note the conditionalization of %G on shared):
*link_command:
%{!fsyntax-only: %{!c:%{!M:%{!MM:%{!E:%{!S:ld %l %X %{o*} %{A} %{d} %{e*} %{m} %{N} %{n} %{r} %{s} %{t} %{u*} %{x} %{z} %{Z} %{!A:%{!nostdlib:%{!nostartfiles:%S}}} %{static:} %{L*} %D %o %{!nostdlib:%{!nodefaultlibs: %{!shared: %G} %L %{!shared: %G}}} %{!A:%{!nostdlib:%{!nostartfiles:%E}}} %{T*} }}}}}}
At least now I don't get error messages at shared library link time.
-------------------------------------------------------------------------------
Lee Iverson SRI International
leei@ai.sri.com 333 Ravenswood Ave., Menlo Park CA 94025
http://www.ai.sri.com/~leei/ (650) 859-3307
next reply other threads:[~1997-12-16 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-16 10:08 Lee Iverson [this message]
1997-12-16 16:17 ` Jeffrey A Law
1997-12-16 23:33 ` Richard Henderson
1997-12-17 9:19 ` Jeffrey A Law
1997-12-17 10:10 ` H.J. Lu
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=199712161724.JAA25082@Canada.AI.SRI.COM \
--to=leei@ai.sri.com \
--cc=egcs@cygnus.com \
/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).