From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/13182 Path: news.gmane.org!.POSTED!not-for-mail From: Jon Chesterfield Newsgroups: gmane.linux.lib.musl.general Subject: Re: How to use MUSL without installing it? Date: Tue, 4 Sep 2018 14:00:03 +0100 Message-ID: References: <20180903232441.0c0e1e868bac54e3b9b31226@asm32.info> <20180904094020.GM4418@port70.net> <20180904143439.121b6867f3e7fb99d4f1b527@asm32.info> <20180904115828.GN4418@port70.net> <20180904152012.ba537d4bb4d775753bfe8f72@asm32.info> <20180904122720.GZ1878@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000068e27305750b3daf" X-Trace: blaine.gmane.org 1536065912 18763 195.159.176.226 (4 Sep 2018 12:58:32 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 4 Sep 2018 12:58:32 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-13198-gllmg-musl=m.gmane.org@lists.openwall.com Tue Sep 04 14:58:28 2018 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1fxAuX-0004fk-Hk for gllmg-musl@m.gmane.org; Tue, 04 Sep 2018 14:58:25 +0200 Original-Received: (qmail 32144 invoked by uid 550); 4 Sep 2018 13:00:32 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 32121 invoked from network); 4 Sep 2018 13:00:31 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=T361SD4bGdF4pwLWrvQ44o+Mt+s2KKdj6L2Pu3WMYds=; b=EuwNL7RiDJAJ4dY/yqYjrPK6XpAsmQJLEQRqGH6Tu9GjgQ9rRbdSiZj65+1XdUUg/Z fchX4ZZXawR+M4JUas9rX9NSy/M6MLboTLGvipSIcEwVjiKr+K10sQr5C9b21RalLAvq Af/dnlFgoaphJqZtMMILR0X5Ql5M7bDL9PbhtPwsxyu1zcNN8cCTfSOnug9v26awYZLJ 7r0vKMLapwnicoNz7dXaI+Rk7jEdq6FKGAXa3NVuedOuZbQFRlWkiT8KYqY3Cl582aOo zax3exo39TJDeA/wF/OF/v9EOBTJ788uFV8KFURFFsYvSHJ9pO0/nvz/DDEoxYlZXQeY kSzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=T361SD4bGdF4pwLWrvQ44o+Mt+s2KKdj6L2Pu3WMYds=; b=ibfE18c4y/it4HK6PNvSeQg5CrMvO9JpnLUcreLjlo2ZgdShMsfqhIZ6vuux8i0Yi7 JzFD4FWD0TT3rplz6SaVXrgDdIWmiYA6tjeyBHmq9dWMx/n08Wf4eFcwaSOTI6kXqbxn ThyDRTo+6ix2iW00214ftbXWGGLPECf9s3jmZljlda1eCa60//v2R14zFDCqCVj0tz4v vPuiDCy9M4beviOD92NGr4HJjDIr79pn7rG1TSbTl0H9vsRgKloTSFZdr8omKDglPtlf 94THdZvglNTXiosY8ZaElsd0HzOXBFaZ33ncwLIJPWv+4smWw8cAWU3sOadZEk7/RQHM qypg== X-Gm-Message-State: APzg51BzBop+RLqx0Fpy6EASEw/sV6CVhLCUiIgVBpE3TG64E/4O4Z1m iH460yBwgsmXoxd2VF4zcH8+HgBqlbLi/T7WeeBW9A== X-Google-Smtp-Source: ANB0VdaiTaeQ/mwFakGWatxAzWSWE/JHm1ypcFVJ57+uFA4FBR1TfxoJQPwpDnSS6WegHpKW0tTqKjtRYX+QPnKfpxk= X-Received: by 2002:a0c:f708:: with SMTP id w8-v6mr28884459qvn.91.1536066018925; Tue, 04 Sep 2018 06:00:18 -0700 (PDT) In-Reply-To: <20180904122720.GZ1878@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:13182 Archived-At: --00000000000068e27305750b3daf Content-Type: text/plain; charset="UTF-8" Hi Rich, I think this would be a great feature. A relative path to the loader means applications can run from wherever the user puts them. Currently achievable with static linking. I've been considering linking an application into the (modified) loader to get a similar result. I think that's workable but haven't cut the code yet. Could you sketch the design you have in mind? Thanks, Jon I'm actually working on a design to allow direct invocation of > dynamic-linked programs without absolute dynamic linker paths, but it > will be a while before it's done and included in musl. > > Rich > --00000000000068e27305750b3daf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Rich,=

I think this would be a g= reat feature. A relative path to the loader means applications can run from= wherever the user puts them. Currently achievable with static linking.

I've been considering lin= king an application into the (modified) loader to get a similar result. I t= hink that's workable but haven't cut the code yet.

Could you sketch the design you have in mi= nd?

Thanks,

Jon


I'm actually working on a design to allow direct invocation of
dynamic-linked programs without absolute dynamic linker paths, but it
will be a while before it's done and included in musl.

Rich
--00000000000068e27305750b3daf--