This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: libstdc++ soname in egcs 1.1 and 1.0.3


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?

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.

Franz.



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]