From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26018 invoked by alias); 3 Sep 2009 05:08:14 -0000 Received: (qmail 26008 invoked by uid 22791); 3 Sep 2009 05:08:12 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from lo.gmane.org (HELO lo.gmane.org) (80.91.229.12) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 03 Sep 2009 05:08:08 +0000 Received: from list by lo.gmane.org with local (Exim 4.50) id 1Mj4YH-0002uS-FQ for gcc@gcc.gnu.org; Thu, 03 Sep 2009 07:08:05 +0200 Received: from 64-201-202-141.regn.hsdb.sasknet.sk.ca ([64.201.202.141]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 03 Sep 2009 07:08:05 +0200 Received: from dirtyepic by 64-201-202-141.regn.hsdb.sasknet.sk.ca with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 03 Sep 2009 07:08:05 +0200 To: gcc@gcc.gnu.org From: Ryan Hill Subject: Re: libstdc++.so.6.0.*-gdb.py might be installed at the wrong place Date: Thu, 03 Sep 2009 05:08:00 -0000 Message-ID: <20090902230819.49f3734d@gentoo.org> References: <4A68CD35.1060001@starynkevitch.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/0XD_cPTQDA4=wWH0Io+muHa"; protocol="application/pgp-signature" X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-09/txt/msg00063.txt.bz2 --Sig_/0XD_cPTQDA4=wWH0Io+muHa Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-length: 1631 On Fri, 24 Jul 2009 09:51:07 -0600 Tom Tromey wrote: > >>>>> "Basile" =3D=3D Basile STARYNKEVITCH wri= tes: > Basile> Shouldn't a python script for gdb be installed outside of a dire= ctory > Basile> supposed to contain only ELF libraries? Wouldn't a gdb specific > Basile> subdirectory be a more appropriate place? >=20 > Perhaps. It is a problem of several parts. Basically, gdb and all > possible users of this interface must agree on where to install such > "hook" files. >=20 > I chose to name the .py files after the libraries and install them > alongside the libraries because it is simple and will not result in any > naming clash. >=20 > There is also the option of installing these files underneath the > separate debug directory. However, gcc has no knowledge of that. I > assume that distros will solve this themselves by moving the file after > make install. 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/libst= dc++.so.6.0.14-gdb.py is not an ELF file - it has the wrong magic bytes at = the start. /sbin/ldconfig: /usr/lib/gcc/x86_64-unknown-linux-gnu/4.5.0-pre9999/32/li= bstdc++.so.6.0.14-gdb.py is not an ELF file - it has the wrong magic bytes = at the start. --=20 fonts, Character is what you are in the dark. gcc-porting, wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 --Sig_/0XD_cPTQDA4=wWH0Io+muHa Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc Content-length: 198 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) iEYEARECAAYFAkqfT0gACgkQiqiDRvmkBmIAZgCg2KcAN6x5DcviyxH8JX+XKJUI cs4An13dqoqRNu2VCgAKh4OOn9n0Abzl =8k7T -----END PGP SIGNATURE----- --Sig_/0XD_cPTQDA4=wWH0Io+muHa--