This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++ soname in egcs 1.1 and 1.0.3
- To: Franz dot Sirl-kernel at lauterbach dot com
- Subject: Re: libstdc++ soname in egcs 1.1 and 1.0.3
- From: Manfred Hollstein <manfred at s-direktnet dot de>
- Date: Fri, 26 Jun 1998 12:00:41 +0200 (MET DST)
- Cc: carlo at runaway dot xs4all dot nl, egcs at cygnus dot com
- References: <199806251557.RAA05432@jolan.ppro> <13713.3687.566331.408795@slsvhmt> <13715.11904.83561.701956@slsvhmt> <E0ypV80-0006dq-00@ks.sel.alcatel.de>
- Reply-To: manfred at s-direktnet dot de, Manfred dot Hollstein at ks dot sel dot alcatel dot de
On Fri, 26 June 1998, 11:48:40, Franz.Sirl-kernel@lauterbach.com wrote:
> At 07:18 26.06.98 , Manfred Hollstein wrote:
> >On Thu, 25 June 1998, 17:57:08, carlo@runaway.xs4all.nl wrote:
> >
> > > Manfred wrote about libstdc++:
> > > | Yes! We should definitely change
> > > |
> > > | VERSION = 2.8.0
> > > |
> > > | to
> > > |
> > > | VERSION = 2.9.0
> > >
> > > Leaving it at 2.8.0 is definitely, positively, wrong.
> > >
> > > But bumping it to 2.9.0 could still cause compilation
> > > with gcc-2.8.x to use it too.
> > > You still can only have one libstdc++.so symbolic link;
> > > so every time you switch compiler you need to change
> > > that link, right?. I am not sure if that is the same
> > > problem though :)
> >
> >Fortunately, we now have the new flag
> `--enable-version-specific-runtime-libs',
> >which installs libstdc++.{a,so*,sl*} and its include files in the
> >compiler specific subdirectory named by the make macro "$(libsubdir)".
>
> Hmm, two questions (I'm no shared lib expert):
> - would it harm anything if the libraries got always installed in eg.
> /usr/lib _and_ $(libsuddir)? So one would have at least a reference copy
> available
> - is linking from /usr/lib to $(libsubdir) ok?
If you're only interested in Linux, then yes, as long as _only_ the
real file libstdc++.so.x.y.z (and not libstdc++.so) is linked.
But, on SunOS this would fail, because the bloody ld.so there
will always happily use the lib with the highest version number :-(
>
> I wonder what's the best thing to do on Linux, since I also could modify
> /etc/ld.so.conf on the fly and add $(libsubdir) while installing the RPM.
For me defining LD_RUN_PATH at linktime seems to be the best solution.
>
> Franz.
>
manfred