Hi All,

I found these libraries hanging around. Should I be deleting them or am I
going to bork my system? Wouldn't mind leaving well alone if there is a
suspicion that I may break things.
================================================
# qfile -o $(find /lib /usr/lib -name "*.la")/lib/libattr.la
/lib/libacl.la
/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.la
/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libsupc++.la
/usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libg2c.la
/usr/lib/libopcodes.la
/usr/lib/libucl.la
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libsupc++.la
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libg2c.la
/usr/lib/alsaplayer/interface/libtext_interface.la
/usr/lib/alsaplayer/interface/libdaemon_interface.la
/usr/lib/libMrm.la
/usr/lib/libGL.la
/usr/lib/libUil.la
/usr/lib/libXm.la
/usr/lib/libbfd.la
================================================

--
Regards,
Mick

On Samstag, 1. Dezember 2007, Mick wrote:
> Hi All,
>
> I found these libraries hanging around. Should I be deleting them or am I
> going to bork my system? Wouldn't mind leaving well alone if there is a
> suspicion that I may break things.
> ================================================
> # qfile -o $(find /lib /usr/lib -name "*.la")/lib/libattr.la
> /lib/libacl.la
> /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.la
> /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libsupc++.la
> /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libg2c.la
> /usr/lib/libopcodes.la
> /usr/lib/libucl.la
> /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la
> /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libsupc++.la
> /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libg2c.la
> /usr/lib/alsaplayer/interface/libtext_interface.la
> /usr/lib/alsaplayer/interface/libdaemon_interface.la
> /usr/lib/libMrm.la
> /usr/lib/libGL.la
> /usr/lib/libUil.la
> /usr/lib/libXm.la
> /usr/lib/libbfd.la
> ================================================

usually keeping them breaks things.

--
Conclusions
In a straight-up fight, the Empire squashes the Federation like a bug. Even
with its numerical advantage removed, the Empire would still squash the
Federation like a bug. Accept it. -Michael Wong
--
gentoo-user@gentoo.org mailing list

On Saturday 01 December 2007, Hemmann, Volker Armin wrote:
> On Samstag, 1. Dezember 2007, Mick wrote:
> > Hi All,
> >
> > I found these libraries hanging around. Should I be deleting them or am
> > I going to bork my system? Wouldn't mind leaving well alone if there is
> > a suspicion that I may break things.
> > ================================================
> > # qfile -o $(find /lib /usr/lib -name "*.la")/lib/libattr.la
> > /lib/libacl.la
> > /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.la
> > /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libsupc++.la
> > /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libg2c.la
> > /usr/lib/libopcodes.la
> > /usr/lib/libucl.la
> > /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la
> > /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libsupc++.la
> > /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libg2c.la
> > /usr/lib/alsaplayer/interface/libtext_interface.la
> > /usr/lib/alsaplayer/interface/libdaemon_interface.la
> > /usr/lib/libMrm.la
> > /usr/lib/libGL.la
> > /usr/lib/libUil.la
> > /usr/lib/libXm.la
> > /usr/lib/libbfd.la
> > ================================================
>
> usually keeping them breaks things.

Fair enough, but nothing seems broken so far . . .
--
Regards,
Mick

On Samstag, 1. Dezember 2007, Mick wrote:
> On Saturday 01 December 2007, Hemmann, Volker Armin wrote:
> > On Samstag, 1. Dezember 2007, Mick wrote:
> > > Hi All,
> > >
> > > I found these libraries hanging around. Should I be deleting them or
> > > am I going to bork my system? Wouldn't mind leaving well alone if
> > > there is a suspicion that I may break things.
> > > ================================================
> > > # qfile -o $(find /lib /usr/lib -name "*.la")/lib/libattr.la
> > > /lib/libacl.la
> > > /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.la
> > > /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libsupc++.la
> > > /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libg2c.la
> > > /usr/lib/libopcodes.la
> > > /usr/lib/libucl.la
> > > /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la
> > > /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libsupc++.la
> > > /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libg2c.la
> > > /usr/lib/alsaplayer/interface/libtext_interface.la
> > > /usr/lib/alsaplayer/interface/libdaemon_interface.la
> > > /usr/lib/libMrm.la
> > > /usr/lib/libGL.la
> > > /usr/lib/libUil.la
> > > /usr/lib/libXm.la
> > > /usr/lib/libbfd.la
> > > ================================================
> >
> > usually keeping them breaks things.
>
> Fair enough, but nothing seems broken so far . . .

sometimes the breakage is hidden and subtle - but for example stale
libstdcc.la files are known to break compilation of c++ code (like qt, kde
and other cool stuff). It is usually a good idea to remove a gcc-dir if there
are only orphaned *la files left.

btw libGL.la is generated by eselect opengl.

--
gentoo-user@gentoo.org mailing list

On Saturday 01 December 2007, Hemmann, Volker Armin wrote:
> On Samstag, 1. Dezember 2007, Mick wrote:
> > On Saturday 01 December 2007, Hemmann, Volker Armin wrote:
> > > On Samstag, 1. Dezember 2007, Mick wrote:
> > > > Hi All,
> > > >
> > > > I found these libraries hanging around. Should I be deleting them or
> > > > am I going to bork my system? Wouldn't mind leaving well alone if
> > > > there is a suspicion that I may break things.
> > > > ================================================
> > > > # qfile -o $(find /lib /usr/lib -name "*.la")/lib/libattr.la
> > > > /lib/libacl.la
> > > > /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libstdc++.la
> > > > /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libsupc++.la
> > > > /usr/lib/gcc/i686-pc-linux-gnu/3.4.4/libg2c.la
> > > > /usr/lib/libopcodes.la
> > > > /usr/lib/libucl.la
> > > > /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la
> > > > /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libsupc++.la
> > > > /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libg2c.la
> > > > /usr/lib/alsaplayer/interface/libtext_interface.la
> > > > /usr/lib/alsaplayer/interface/libdaemon_interface.la
> > > > /usr/lib/libMrm.la
> > > > /usr/lib/libGL.la
> > > > /usr/lib/libUil.la
> > > > /usr/lib/libXm.la
> > > > /usr/lib/libbfd.la
> > > > ================================================
> > >
> > > usually keeping them breaks things.
> >
> > Fair enough, but nothing seems broken so far . . .
>
> sometimes the breakage is hidden and subtle - but for example stale
> libstdcc.la files are known to break compilation of c++ code (like qt, kde
> and other cool stuff). It is usually a good idea to remove a gcc-dir if
> there are only orphaned *la files left.
>
> btw libGL.la is generated by eselect opengl.

Hmm, I wonder if this 'stale' gcc-3.4.5 has something to do with it:
===============================================
# gcc-config -l
[1] i686-pc-linux-gnu-3.4.5
[2] i686-pc-linux-gnu-3.4.5-hardened
[3] i686-pc-linux-gnu-3.4.5-hardenednopie
[4] i686-pc-linux-gnu-3.4.5-hardenednopiessp
[5] i686-pc-linux-gnu-3.4.5-hardenednossp
[6] i686-pc-linux-gnu-4.1.2 *

# emerge -Cpv gcc-3.4.5

>>> These are the packages that would be unmerged:

--- Couldn't find 'gcc-3.4.5' to unmerge.

>>> No packages selected for removal by unmerge
===============================================

The strange thing is that the orphan libs are from gcc-3.4.4. Anyway, I'll
delete them now as you recommend.
--
Regards,
Mick

On Sunday 02 December 2007, Mick wrote:
> On Saturday 01 December 2007, Hemmann, Volker Armin wrote:

> > sometimes the breakage is hidden and subtle - but for example stale
> > libstdcc.la files are known to break compilation of c++ code (like qt,
> > kde and other cool stuff). It is usually a good idea to remove a gcc-dir
> > if there are only orphaned *la files left.
> >
> > btw libGL.la is generated by eselect opengl.
>
> Hmm, I wonder if this 'stale' gcc-3.4.5 has something to do with it:
> ===============================================
> # gcc-config -l
> [1] i686-pc-linux-gnu-3.4.5
> [2] i686-pc-linux-gnu-3.4.5-hardened
> [3] i686-pc-linux-gnu-3.4.5-hardenednopie
> [4] i686-pc-linux-gnu-3.4.5-hardenednopiessp
> [5] i686-pc-linux-gnu-3.4.5-hardenednossp
> [6] i686-pc-linux-gnu-4.1.2 *
>
> # emerge -Cpv gcc-3.4.5
>
> >>> These are the packages that would be unmerged:
>
> --- Couldn't find 'gcc-3.4.5' to unmerge.
>
> >>> No packages selected for removal by unmerge
>
> ===============================================
>
> The strange thing is that the orphan libs are from gcc-3.4.4. Anyway, I'll
> delete them now as you recommend.

I just noticed that /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4 contains a whole
lot of other packages which were not identified by qfile as stale:
===============================================
# ls -la /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/
total 20891
drwxr-xr-x 4 root root 976 Dec 8 2004 .
drwxr-xr-x 3 root root 72 Oct 27 2004 ..
-rwxr-xr-x 1 root root 3797008 Dec 8 2004 cc1
-rwxr-xr-x 1 root root 4429280 Dec 8 2004 cc1plus
-rwxr-xr-x 1 root root 102048 Dec 8 2004 collect2
-rw-r--r-- 1 root root 1680 Dec 8 2004 crtbegin.o
-rw-r--r-- 1 root root 2216 Dec 8 2004 crtbeginS.o
-rw-r--r-- 1 root root 2076 Dec 8 2004 crtbeginT.o
-rw-r--r-- 1 root root 1344 Dec 8 2004 crtend.o
-rw-r--r-- 1 root root 1544 Dec 8 2004 crtendS.o
-rwxr-xr-x 1 root root 4219688 Dec 8 2004 f771
drwxr-xr-x 3 root root 512 Dec 8 2004 include
drwxr-xr-x 3 root root 224 Dec 8 2004 install-tools
-rw-r--r-- 1 root root 1182 Dec 8 2004 libfrtbegin.a
-rw-r--r-- 1 root root 364042 Dec 8 2004 libg2c.a
-rwxr-xr-x 1 root root 785 Dec 8 2004 libg2c.la
lrwxrwxrwx 1 root root 15 Mar 26 2006 libg2c.so -> libg2c.so.0.0.0
lrwxrwxrwx 1 root root 15 Mar 26 2006 libg2c.so.0 -> libg2c.so.0.0.0
-rwxr-xr-x 1 root root 129876 Dec 8 2004 libg2c.so.0.0.0
-rw-r--r-- 1 root root 2920182 Dec 8 2004 libgcc.a
-rw-r--r-- 1 root root 294570 Dec 8 2004 libgcc_eh.a
lrwxrwxrwx 1 root root 13 Mar 26 2006 libgcc_s.so -> libgcc_s.so.1
-rw-r--r-- 1 root root 38644 Dec 8 2004 libgcc_s.so.1
-rw-r--r-- 1 root root 184448 Dec 8 2004 libiberty.a
-rw-r--r-- 1 root root 1874656 Dec 8 2004 libstdc++.a
-rwxr-xr-x 1 root root 969 Dec 8 2004 libstdc++.la
lrwxrwxrwx 1 root root 18 Mar 26 2006 libstdc++.so -> libstdc++.so.5.0.6
lrwxrwxrwx 1 root root 18 Mar 26 2006 libstdc++.so.5 ->
libstdc++.so.5.0.6
-rwxr-xr-x 1 root root 808208 Dec 8 2004 libstdc++.so.5.0.6
-rw-r--r-- 1 root root 1965794 Dec 8 2004 libstdc++_pic.a
-rw-r--r-- 1 root root 173834 Dec 8 2004 libsupc++.a
-rwxr-xr-x 1 root root 909 Dec 8 2004 libsupc++.la
-rw-r--r-- 1 root root 4726 Dec 8 2004 specs
===============================================

Should I remove the lot? (gcc-3.3.4 was unmerged from my system years ago).
--
Regards,
Mick

On Sunday 02 December 2007 10:24:50 Mick wrote:
> Should I remove the lot? *(gcc-3.3.4 was unmerged from my system years
> ago).

Yes.

--
Bo Andresen

On Monday 03 December 2007, Bo Ørsted Andresen wrote:
> On Sunday 02 December 2007 10:24:50 Mick wrote:
> > Should I remove the lot? *(gcc-3.3.4 was unmerged from my system years
> > ago).
>
> Yes.

Thanks. Just got rid of them.
--
Regards,
Mick