From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4762 Path: news.gmane.org!not-for-mail From: u-igbb@aetey.se Newsgroups: gmane.linux.lib.musl.general Subject: Re: MUSL_LIBRARY_PATH ? Date: Tue, 1 Apr 2014 18:19:08 +0200 Message-ID: <20140401161908.GJ13904@example.net> References: Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1396369186 5668 80.91.229.3 (1 Apr 2014 16:19:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 1 Apr 2014 16:19:46 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-4766-gllmg-musl=m.gmane.org@lists.openwall.com Tue Apr 01 18:19:40 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1WV1PU-0006vH-5a for gllmg-musl@plane.gmane.org; Tue, 01 Apr 2014 18:19:36 +0200 Original-Received: (qmail 21984 invoked by uid 550); 1 Apr 2014 16:19:35 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 21964 invoked from network); 1 Apr 2014 16:19:34 -0000 X-T2-Spam-Status: No, hits=0.8 required=5.0 tests=BAYES_50 Received-SPF: none receiver=mailfe07.swip.net; client-ip=83.133.106.73; envelope-from=u-igbb@aetey.se Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Xref: news.gmane.org gmane.linux.lib.musl.general:4762 Archived-At: Hi John, On Tue, Apr 01, 2014 at 10:11:57AM -0400, John Mudd wrote: > But I run into trouble when I start setting LD_LIBRARY_PATH so that Python > can locate the Readline and other libs. The musl built Python works but > these libs start causing native program to fail. e.g. "vim: error while > loading shared libraries: /usr/lib/i386-linux-gnu/libc.so: invalid ELF > header". You seem to encounter the very problem which the newly discussed --library-path solves. You may need to run your musl-linked binaries via wrappers, starting them like /..../libc.so --library-path /...yourseparatelibplace /the...binary [args] Let you look at the recent posts mentioning LD_LIBRARY_PATH. (Note that hacks like "MUSL_LIBRARY_PATH" do not allow using in the same process tree different versions/instances of libraries, iow being about as much broken as LD_LIBRARY_PATH) Regards, Rune