public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Helge Hess <hh@mdlink.de>
To: law@cygnus.com
Cc: egcs@egcs.cygnus.com
Subject: Re: shared libobjc & multilibs ?
Date: Wed, 30 Jun 1999 15:43:00 -0000	[thread overview]
Message-ID: <3753E1F2.6C5CBF0B@mdlink.de> (raw)
Message-ID: <19990630154300._YC2lbWdDKe5KZgmGe-AJyO9HyNd4kguQrWj9tqgPio@z> (raw)
In-Reply-To: <31982.928177399@upchuck.cygnus.com>

Jeffrey A Law wrote:
>   In message <37526033.6B800C06@mdlink.de>you write:
>   > Hi there,
>   >
>   > what would be the best approach to make egcs support building a shared
>   > libobjc ? I can see that libstdc++ can be build shared and static, so
>   > this should be possible.
>   >
>   > Does libstdc++ use this 'multilib' feature or does it use a custom
>   > Makefile ? If so, where can I read more about 'multilibs', the configure
>   > documentation on this topic isn't very extensive ? Is there any less
>   > complicated example of multilibs than libstdc++ ?
> See the libiberty makefiles and configure fragments.

libiberty isn't built as a shared library (at least not, when specifying
--enable-shared). I had a look at some makefiles in gcc and it seems to
me that multilibs aren't the right thing to build static and shared
library-versions. I have the impression (I don't fully understand the
gcc makefiles) that shared compilation needs to be supported 'by-hand'
in the appropriate Makefile.in's.

libstdc++ is the only library which is also build shared on my system,
so it seems I'll need to have a look at this.

Helge
-- 
MDlink online service center
http://www.mdlink.de/

  parent reply	other threads:[~1999-06-30 15:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-31  3:07 Helge Hess
1999-05-31 12:07 ` Jeffrey A Law
1999-05-31 12:21   ` Marcus G. Daniels
1999-05-31 13:40     ` Jeffrey A Law
1999-05-31 21:36       ` Jeffrey A Law
1999-05-31 21:36     ` Marcus G. Daniels
1999-05-31 21:36   ` Jeffrey A Law
1999-06-01  6:33   ` Helge Hess [this message]
1999-06-01  8:46     ` Jeffrey A Law
1999-06-30 15:43       ` Jeffrey A Law
1999-06-30 15:43     ` Helge Hess
1999-05-31 21:36 ` Helge Hess

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=3753E1F2.6C5CBF0B@mdlink.de \
    --to=hh@mdlink.de \
    --cc=egcs@egcs.cygnus.com \
    --cc=law@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).