This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: shared libobjc & multilibs ?
- To: law at cygnus dot com
- Subject: Re: shared libobjc & multilibs ?
- From: Helge Hess <hh at mdlink dot de>
- Date: Tue, 01 Jun 1999 15:36:50 +0200
- CC: egcs at egcs dot cygnus dot com
- Organization: MDlink online service center
- References: <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/