On Tue, 2006-11-28 at 17:52 +0100, Michael Haubenwallner wrote:
> <snip>
> >
> > > Reflecting all that, I become more being for copying libstdc++ into
> > > EPREFIX/lib in addition to libgcc_s, and let SONAME do its work.
> >
> > ... and libgcj and and and... If feels to fugly to do that. gcc-config
> > only copies libgcc_s because of backwards compatibility if I got it
> > right, for apps that were linked against libgcc_s in that place which
> > will break if you remove it. I'd like no application to ever link
> > against a gcc lib in usr/lib.
>
> What are the gcc libs different than libs from any other package, except
> that they are more basic ? What about glibc (on native Gentoo) ?
> For me, glibc and gcc are somehow on the same very basic level...
>
> IMO gcc is one of that rare packages where 'soname' is used correctly.
> To me, it seems that gcc devs try harder than other package's devs to
> ensure that a newer lib is compatible to an older one with same
> 'soname'.
> Maybe gcc-config should ensure the lib{gcc_s,stdc++,...}.so* symlinks
> point to the one from most recent available gcc in EPREFIX/lib,
> regardless of which gcc is actually selected ?
Look what I've just found on Redhat Enterprise Linux :-o
$ ls -l /usr/lib/libstdc++* /usr/lib/libgcj*
lrwxrwxrwx 1 root root 15 Apr 13 2006 /usr/lib/libgcj.so.5 ->
libgcj.so.5.0.0
-rwxr-xr-x 1 root root 10828056 Dec 20 2005 /usr/lib/libgcj.so.5.0.0
lrwxrwxrwx 1 root root 15 Apr 13 2006 /usr/lib/libgcj.so.6 ->
libgcj.so.6.0.0
-rwxr-xr-x 1 root root 17075916 Jan 6 2006 /usr/lib/libgcj.so.6.0.0
lrwxrwxrwx 1 root root 18 Apr 13 2006 /usr/lib/libgcjawt.so.6 ->
libgcjawt.so.6.0.0
-rwxr-xr-x 1 root root 4220 Jan 6 2006 /usr/lib/libgcjawt.so.6.0.0
-rwxr-xr-x 1 root root 258288 Dec 14 2004
/usr/lib/libstdc++-2-libc6.1-1-2.9.0.so
-rwxr-xr-x 1 root root 268428 Dec 14 2004
/usr/lib/libstdc++-3-libc6.2-2-2.10.0.so
lrwxrwxrwx 1 root root 30 Apr 13 2006 /usr/lib/libstdc++-libc6.1-1.so.2
-> libstdc++-2-libc6.1-1-2.9.0.so
lrwxrwxrwx 1 root root 31 Apr 13 2006 /usr/lib/libstdc++-libc6.2-2.so.3
-> libstdc++-3-libc6.2-2-2.10.0.so
lrwxrwxrwx 1 root root 18 Apr 13 2006 /usr/lib/libstdc++.so.5 ->
libstdc++.so.5.0.7
-rwxr-xr-x 1 root root 733488 Dec 1 2004 /usr/lib/libstdc++.so.5.0.7
lrwxrwxrwx 1 root root 18 Apr 13 2006 /usr/lib/libstdc++.so.6 ->
libstdc++.so.6.0.3
-rwxr-xr-x 1 root root 807680 Dec 20 2005 /usr/lib/libstdc++.so.6.0.3
$ ls -l /lib/libgcc*
-rwxr-xr-x 1 root root 31184 Dec 20 2005 /lib/libgcc_s-3.4.5-20051201.so.1
lrwxrwxrwx 1 root root 28 Apr 13 2006 /lib/libgcc_s.so.1 ->
libgcc_s-3.4.5-20051201.so.1
For me, having gcc-config to manage copies of gcc libs in /lib (for
libgcc_s*) and /usr/lib (for the others) is not that bad...
/haubi/
--
[EMAIL PROTECTED] mailing list
