Date: Thu, 5 Sep 2013 08:41:29 +0100 From: Jonathan Anderson <jonathan.anderson@ieee.org> To: Konstantin Belousov <kostikbel@gmail.com> Cc: Dag-Erling Sm??rgrav <des@des.no>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: /usr/lib/private Message-ID: <CAMGEAwByA5ewSD=5nO4GyYdnAEWyJgczQsb_eOUAScMLcfJRJQ@mail.gmail.com> In-Reply-To: <20130905023703.GN41229@kib.kiev.ua> References: <86zjrut4an.fsf@nine.des.no> <20130905023703.GN41229@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Is there any reason not to make it /private/usr/lib (or /private/usr/lib/platform)? I could see us wanting a /private/usr/include in the future for e.g. LLVM/Clang headers that things in base (e.g. lldb) might use but whose stability we don't want to be responsible for. Jon On Thursday, 5 September 2013, Konstantin Belousov wrote: > On Tue, Sep 03, 2013 at 03:37:04PM +0200, Dag-Erling Sm??rgrav wrote: > > The attached patch introduces a mechanism for installing libraries into > > /usr/lib/private, which is not in the standard rtld search path, and > > setting -rpath accordingly for programs and libraries that need one of > > those libraries. Private libraries are meant for internal use only and > > need to be kept out of the way so they don't conflict with similarly- > > named libraries installed by ports. The first to go is libssh (which > > shouldn't even exist, but that's another story). > > > > There is one issue this patch does not address: 32-bit binaries which > > reference private libraries on a 64-bit system won't find them. This > > can be fixed by having rtld automagically translate /usr/lib/private to > > /usr/lib32/private when appropriate, which is rather gross. > > You could consider using the $PLATFORM token in the rpath, so that > you use /usr/lib/private-<hw-machine-arch> as the installation target. > -- Jonathan Anderson jonathan.anderson@ieee.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMGEAwByA5ewSD=5nO4GyYdnAEWyJgczQsb_eOUAScMLcfJRJQ>