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 25263 invoked from network); 13 May 2020 21:51:34 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 13 May 2020 21:51:34 -0000 Received: (qmail 20218 invoked by uid 550); 13 May 2020 21:51:30 -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 20197 invoked from network); 13 May 2020 21:51:29 -0000 Date: Wed, 13 May 2020 17:51:17 -0400 From: Rich Felker To: musl@lists.openwall.com Message-ID: <20200513215115.GC21576@brightrain.aerifal.cx> References: <20200510163555.GU21576@brightrain.aerifal.cx> <20200510215257.GW21576@brightrain.aerifal.cx> <20200513143759.GV21576@brightrain.aerifal.cx> <20200513185551.GZ21576@brightrain.aerifal.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] Re: [musl-cross-make] [PATCH v2] litecross: Fix system header dir when building native toolchains On Wed, May 13, 2020 at 08:04:10PM +0000, Laurent Bercot wrote: > >My patch is intended to just fix this incorrect path, not to change > >the meaning of NATIVE=y. 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. Would you be happy with TARGET=HOST=... giving this behavior while NATIVE=y additionally gives a real native compiler (that uses the existing library ecosystem)? Or should I make a new name for the latter? Rich