From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4761 Path: news.gmane.org!not-for-mail From: John Mudd Newsgroups: gmane.linux.lib.musl.general Subject: MUSL_LIBRARY_PATH ? Date: Tue, 1 Apr 2014 10:11:57 -0400 Message-ID: Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c269c266dff404f5fbc1ff X-Trace: ger.gmane.org 1396361561 3498 80.91.229.3 (1 Apr 2014 14:12:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 1 Apr 2014 14:12:41 +0000 (UTC) To: musl Original-X-From: musl-return-4765-gllmg-musl=m.gmane.org@lists.openwall.com Tue Apr 01 16:12:36 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 1WUzQU-0002yh-Fw for gllmg-musl@plane.gmane.org; Tue, 01 Apr 2014 16:12:30 +0200 Original-Received: (qmail 13339 invoked by uid 550); 1 Apr 2014 14:12:29 -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 13329 invoked from network); 1 Apr 2014 14:12:28 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=cecQV2hlcQ13fIlwu4eGe9M26UqsijQPeUWoV7lQ8wg=; b=ZQ7nUvAfw4B1prmDzUyTnV8vIb+FrVI99ctyFJHVHKHPubyqnaCxTbD/JyanzE52Nn j2BGzekIyiGW06X6jo2QODZT/4ur/mBlqn9oz2JDV6VbvSSTT1uUxhDy6Yrpdr0Xa081 SmJ6dDHt4NV7cFnmsRyVtkmJ0i3jrLsfVWMSeDYOh5G8QiZFlGfct5XqkbOOFBjmd6Ha FaFKBfuazYP1CzCJyQIABy0pMcC1B9K7Q7ti8/xIb/yxbnzeZNTkvyy5hv39ZMDNS/Bj sevU0kRKH2N3wFsgzQIv4d30ZH1o2Xvluf5ZXdFfjQp5iNV1NFWQLw7E+eBTw01dmKTB u3VA== X-Received: by 10.112.167.202 with SMTP id zq10mr252036lbb.76.1396361537181; Tue, 01 Apr 2014 07:12:17 -0700 (PDT) Xref: news.gmane.org gmane.linux.lib.musl.general:4761 Archived-At: --001a11c269c266dff404f5fbc1ff Content-Type: text/plain; charset=ISO-8859-1 Possible dumb question... I built Python using musl. Not easy but it works. I also build libraries for Ncurses, Readline, Zlib, OpenSSL, BZip2 so that all of that so the corresponding Python modules are working. Then I installed setuptools and pip in Python. Then I used pip to download and install several modules: Requests, ConcurrentLogHandlerand Psutil. All using musl. I experimented with dynamic and static binding for the musl lib. I lean toward dynamic because I may have a need for the "shared" version of Python. So now I can run this on older machines. That helps me because I need to deploy on old boxes. Upgrading the O/S is not an option. 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". And there's the ld-musl-i386.so.1 file in dynamic mode. I specified --syslibdir=/tmp when I build musl so that's where I place the lib. It works but I'd like more flexibility. I'm naive so my question is... how about a separate MUSL_LIBRARY_PATH shell variable. Just like LD_LIBRARY_PATH but specific to programs built using musl. That way I assume I could mix my musl Python with native apps. As long as I'm asking, can MUSL_LIBRARY_PATH also specify where to find ld-musl-i386.so.1? That might be crazy because a dynamic musl program can't start without the lib so it can't interrogate a shell variable? I'm still asking even though it might require magic. John --001a11c269c266dff404f5fbc1ff Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Possible dumb question...

I built= Python using musl. Not easy but it works.=A0

I also bui= ld libraries for Ncurses,=A0Readline,=A0Zlib,=A0OpenSSL,=A0BZip2 so that al= l of that so the corresponding Python modules are working. Then I installed= =A0setuptools and pip in Python. Then I used pip to download and install se= veral modules: Requests,=A0ConcurrentLogHandlerand Psutil. All using musl.<= /div>

I experimented with dynamic and static binding for the = musl lib. I lean toward dynamic because I may have a need for the "sha= red" version of Python.

So now I can run this= on older machines. That helps me because I need to deploy on old boxes. Up= grading the O/S is not an option.

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. =A0&= quot;vim: error while loading shared libraries: /usr/lib/i386-linux-gnu/lib= c.so: invalid ELF header".=A0

And there's the=A0ld-musl-i386.so.1 file in dynamic= mode. I specified=A0--syslibdir=3D/tmp when I build musl so that's whe= re I place the lib. It works but I'd like more flexibility.
<= br>
I'm naive so my question is... how about a separate=A0MUSL_L= IBRARY_PATH shell variable. Just like=A0LD_LIBRARY_PATH but specific to pro= grams built using musl. That way I assume I could mix my musl Python with n= ative apps.=A0

As long as I'm asking, can=A0MUSL_LIBRARY_PATH also= specify where to find=A0ld-musl-i386.so.1? That might be crazy because a d= ynamic musl program can't start without the lib so it can't interro= gate a shell variable? I'm still asking even though it might require ma= gic.

John


--001a11c269c266dff404f5fbc1ff--