shared libobjc & multilibs ?

Jeffrey A Law law@cygnus.com
Wed Jun 30 15:43:00 GMT 1999


  In message < 3753E1F2.6C5CBF0B@mdlink.de >you write:
  > libiberty isn't built as a shared library (at least not, when specifying
  > --enable-shared).
But most of the hooks one needs to build a shared library can be found in
libiberty.  In particular the code to set up and build both static and sharable
versions of each .o file for each multilib.

  > 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.
You are correct.  multilibs are for dealing with processor variants.  If you
want to build shared libraries, you would basically need to build one for each
already existing multilib. 

  > 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.
It's going to need a little work -- it's not going to "just work".

  > 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.
You'll have to look at it for some of the changes, but I strongly recommend 
also
reviewing libiberty. 

jeff



More information about the Gcc mailing list