public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: eoin <eoin.mcquillan@btinternet.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc the gnu linker and the -z extract option
Date: Mon, 28 Jul 2008 09:39:00 -0000	[thread overview]
Message-ID: <488D84EA.2060003@redhat.com> (raw)
In-Reply-To: <18635245.post@talk.nabble.com>

eoin wrote:

>      I'm a new poster here. I am porting some Solaris code over to Linux and
> using the GNU compiler and linker. Now I have a "meta library"(creating a
> "master" shared object from mayny shared objects) which creates fine in
> Solaris but in Linux it doesn't create as a meta library - ldd suggests that
> it depends on the libraries which were previously used to produce the meta
> library on solaris.

What should be in this meta library?  Is it all the contents of all the libraries?

>      Looking into this I can see that with every .so we effectively lose the
> identity and so with a metalibrary what we need to do is to "unravel" the
> .sos to produce the meta library.

"Lose the idenitity?"  I don't know what you mean.

>      I do this in Solaris using the -z extract option. I can't see how to do
> this in Linux using the GNU linker.

Compile every .o file with -fpic.  Make them all into archives with ar.
Link all the archives together into a .so.

Andrew.

  reply	other threads:[~2008-07-28  8:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-24 16:58 eoin
2008-07-28  9:39 ` Andrew Haley [this message]
2008-07-31 17:15 ` eoin
2008-07-31 22:15   ` Andrew Haley

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=488D84EA.2060003@redhat.com \
    --to=aph@redhat.com \
    --cc=eoin.mcquillan@btinternet.com \
    --cc=gcc-help@gcc.gnu.org \
    /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).