From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22130 invoked by alias); 11 Jun 2019 20:34:25 -0000 Mailing-List: contact libc-help-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: libc-help-owner@sourceware.org Received: (qmail 22107 invoked by uid 89); 11 Jun 2019 20:34:25 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=unavailable version=3.3.1 spammy=noloadergmailcom, H*i:sk:6ANT3dm, noloader@gmail.com, H*f:sk:6ANT3dm X-HELO: mail-qt1-f176.google.com Received: from mail-qt1-f176.google.com (HELO mail-qt1-f176.google.com) (209.85.160.176) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 11 Jun 2019 20:34:23 +0000 Received: by mail-qt1-f176.google.com with SMTP id a15so16207236qtn.7 for ; Tue, 11 Jun 2019 13:34:23 -0700 (PDT) Return-Path: Received: from [192.168.8.101] ([67.69.69.230]) by smtp.gmail.com with ESMTPSA id h32sm5110941qte.26.2019.06.11.13.34.19 (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Tue, 11 Jun 2019 13:34:20 -0700 (PDT) Subject: Re: How to set a system-wide library path policy? To: noloader@gmail.com Cc: Binutils , libc-help References: From: Carlos O'Donell Message-ID: Date: Tue, 11 Jun 2019 20:34:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-06/txt/msg00013.txt.bz2 On 6/11/19 3:56 PM, Jeffrey Walton wrote: > On Sun, Jun 9, 2019 at 5:34 PM Jeffrey Walton wrote: >> >> On Fri, Jun 7, 2019 at 4:46 PM Carlos O'Donell wrote: >>> >>> On 6/7/19 10:53 AM, Jeffrey Walton wrote: >>>> I'm having trouble figuring out how to setup library path policy on Fedora 29. >>> >>> The system loader is in glibc. Adding libc-help to the CC. >>> >>>> I need to articulate to the system loader: >>>> >>>> 1. programs in /bin must only link to libs in /lib64 >>>> 2. programs in /usr/bin must only link to libs in /usr/lib64 >>>> 3. programs in /usr/local/bin may use libraries in /usr/local/lib64 or >>>> /usr/lib64 >>> >>> OK. >>> >>>> As far as I know, the distro supplies (1) and (2). They know nothing >>>> about my libraries in /usr/local. When the distro is ready, it will >>>> push updated programs and libraries as needed. The distro binaries >>>> should not use my libraries. >>> >>> Why would your distro binaries use your libraries? Such libraries are >>> not present at static link time when they are built in the Feodra builders. >>> >>> The only reason your distro libraries would be used is if you used >>> LD_LIBRARY_PATH that pointed to them, in which case you would be altering >>> the global search order. >> >> Thanks Carlos, >> >> Here is a Solaris example because I'm updating Git for the 2.20.0 >> release. Linux behaves the same way as Solaris, so there' no material >> difference here. >> ... > > Here's a Ubuntu Bionic Aarch64 example when running apt-get. The stuff > in /usr/local was built for GnuTLS testing. Guile 2.2 was built from > sources: > > Calculating upgrade... Done > The following packages will be upgraded: > dbus dbus-x11 libdbus-1-3 libglib2.0-0 libglib2.0-data libpython2.7 > libpython2.7-minimal libpython2.7-stdlib libpython3.6 libpython3.6-minimal > libpython3.6-stdlib libssl-dev libssl1.1 openssl python2.7 python2.7-minimal > python3.6 python3.6-minimal vim vim-common vim-runtime vim-tiny xxd > ... > Processing triggers for libc-bin (2.27-3ubuntu1) ... > /sbin/ldconfig.real: /usr/local/lib/libguile-2.2.so.1.3.1-gdb.scm is > not an ELF file - it has the wrong magic bytes at the start. > ... The dynamic loader does not normally search /usr/local/lib. The use of ldconfig does not normally scan non-DSOs. Why is it searching /usr/local/lib? Do you have entries in /etc/ld.so.conf to force it to look for libraries in /usr/local/lib? Have extra patches been applied to this glibc to change the behaviour? You should be taking this up with Ubuntu. -- Cheers, Carlos.