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 8364 invoked from network); 22 May 2020 17:54:04 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 22 May 2020 17:54:04 -0000 Received: (qmail 28312 invoked by uid 550); 22 May 2020 17:54:01 -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 28288 invoked from network); 22 May 2020 17:53:59 -0000 Date: Fri, 22 May 2020 13:53:46 -0400 From: Rich Felker To: Hauke Mehrtens Cc: musl@lists.openwall.com, Harald Welte , Alexander Couzens Message-ID: <20200522175346.GZ1079@brightrain.aerifal.cx> References: <20200521202253.GC601762@nataraja> <20200521204048.GJ1079@brightrain.aerifal.cx> <20200521211927.GE601762@nataraja> <20200521214948.GL1079@brightrain.aerifal.cx> <20200522165006.GR2993937@nataraja> <20200522173300.GX1079@brightrain.aerifal.cx> <57f97221-4bf1-1ee1-b06d-13c6c384fba4@hauke-m.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <57f97221-4bf1-1ee1-b06d-13c6c384fba4@hauke-m.de> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] MUSL ignores__attribute__((constructor(priority))) ? On Fri, May 22, 2020 at 07:45:48PM +0200, Hauke Mehrtens wrote: > On 5/22/20 7:33 PM, Rich Felker wrote: > > On Fri, May 22, 2020 at 06:50:06PM +0200, Harald Welte wrote: > >> Hi Rich, > >> > >> On Thu, May 21, 2020 at 05:49:48PM -0400, Rich Felker wrote: > >>>> According to the OpenWRT build I have been provided by a 3rd party, it's > >>>> using musl-1-1.23. > >>> > >>> Can you confirm this to make sure we're not debugging an issue that's > >>> long since fixed? Run /lib/ld-musl-armhf.so.1 as a command and it will > >>> print its version. > >> > >> *sigh*. It was 1.1.20. This specific (vendor) OpenWRT tree was broken in that > >> it used the 1.1.20 source code but called the generated packages and > >> path names 1.1.23 :/ > >> > >> After updating the sources to actual 1.1.23, the constructor order is > >> correct and I can run the unmodified libraries + application just like > >> on glibc. > >> > >> Sorry for the noise then. Normally if something is named 1.1.23 you > >> assume it also is 1.1.23 inside... > > > > OK, I'll inquire with OpenWRT about what's going on here.. > > > Hi, > > Hauke here form OpenWrt, I am just reading this. ;-) > > OpenWrt never shipped musl 1.1.20 or 1.1.23 in any final release. > OpenWrt 19.07 uses musl 1.1.24 > OpenWrt 18.06 uses musl 1.1.19 > I also checked that this is really using this version and not just > claims to do so. > > I assume that some vendor forked a random OpenWrt master state and had a > problem with their broken application and "fixed" it by downgrading > musl, but they only changed the git commit hash which should be used > and not the version number. > > I saw that lynxis just send this patch to use the official tar.gz for > musl and not check musl out from git any more, I assume this is related > to this discussion: > https://patchwork.ozlabs.org/project/openwrt/patch/20200522153626.1398980-1-lynxis@fe80.eu/ Thanks for the quick follow-up!