From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 14225 invoked from network); 13 May 2020 20:04:27 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 13 May 2020 20:04:27 -0000 Received: (qmail 7690 invoked by uid 550); 13 May 2020 20:04:25 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 7669 invoked from network); 13 May 2020 20:04:24 -0000 From: "Laurent Bercot" To: musl@lists.openwall.com Date: Wed, 13 May 2020 20:04:10 +0000 Message-Id: In-Reply-To: References: <20181107064957.1137-1-mforney@mforney.org> <20200323043456.13327-1-mforney@mforney.org> <20200510163555.GU21576@brightrain.aerifal.cx> <20200510215257.GW21576@brightrain.aerifal.cx> <20200513143759.GV21576@brightrain.aerifal.cx> <20200513185551.GZ21576@brightrain.aerifal.cx> User-Agent: eM_Client/7.2.37929.0 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduhedrleeggddugedvucetufdoteggodftvfcurfhrohhfihhlvgemucfpfgfogfftkfevteeunffgpdfqfgfvnecuuegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkfgjfhhrfgggtgfgsehtqhertddtreejnecuhfhrohhmpedfnfgruhhrvghnthcuuegvrhgtohhtfdcuoehskhgrqdguihgvthhlihgstgesshhkrghrnhgvthdrohhrgheqnecuggftrfgrthhtvghrnhepueeihffhueevgedujefggeduueefvedufedtleevieefffeitdeiheethedtvedtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmohguvgepshhmthhpohhuth Subject: Re: [musl] Re: [musl-cross-make] [PATCH v2] litecross: Fix system header dir when building native toolchains >My patch is intended to just fix this incorrect path, not to change >the meaning of NATIVE=3Dy. Such a change should probably involve >coordination of Zach van Rijn and Laurent Bercot, both of whom >distribute pre-built native toolchains (currently containing a usr -> >. symlink). Consumers of those toolchains probably expect a >self-contained, relocatable toolchain, since that's what they are >currently getting. Yes. I don't know about Zach, but what I want from the tool is indeed for it to produce self-contained, relocatable toolchains, whether they are cross- or native. Non-sysrooted toolchains are not very interesting to me: they have value when you are building a distribution, but less so when you are building entirely independently from the existing distribution, which is often the case with musl on glibc-based distros. Also, a sysrooted toolchain is perfectly usable as the system toolchain - it just requires a couple symbolic links. I 100% support fixing mcm and avoiding the need to patch the produced toolchains, but please don't change its semantics. Relocatability and self-containedness are where it's at. -- Laurent