This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++.so.6.0.*-gdb.py might be installed at the wrong place
- From: Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: Ryan Hill <dirtyepic at gentoo dot org>, gcc at gcc dot gnu dot org
- Date: Thu, 3 Sep 2009 19:59:48 +0200
- Subject: Re: libstdc++.so.6.0.*-gdb.py might be installed at the wrong place
- References: <4A68CD35.1060001@starynkevitch.net> <m3prbqrses.fsf@fleche.redhat.com> <20090902230819.49f3734d@gentoo.org> <20090903085142.GD3611@sunsite.ms.mff.cuni.cz>
Hello Jakub,
* Jakub Jelinek wrote on Thu, Sep 03, 2009 at 10:51:42AM CEST:
> On Wed, Sep 02, 2009 at 11:08:19PM -0600, Ryan Hill wrote:
> >
> > I was just wondering if there was any consensus among distros about where to
> > move these. We cannot keep the .py files in the location they're currently
> > installed; ldconfig is far too noisy about it:
> >
> > /sbin/ldconfig: /usr/lib/gcc/x86_64-unknown-linux-gnu/4.5.0-pre9999/libstdc++.so.6.0.14-gdb.py is not an ELF file - it has the wrong magic bytes at the start.
> ldconfig by default certainly doesn't search gcc private directories, if you
> let ldconfig search there by adding it to its configuration, it would be
> admin error.
'libtool --mode=install' will invoke 'ldconfig -n' on the directory
it installs libraries in (e.g., in order to fix symlinks), which will
cause this complaint as well.
Cheers,
Ralf