From: Alexander 'lynxis' Couzens <lynxis@fe80.eu>
To: Rich Felker <dalias@libc.org>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
musl@lists.openwall.com, Harald Welte <laforge@gnumonks.org>
Subject: Re: [musl] MUSL ignores__attribute__((constructor(priority))) ?
Date: Sat, 23 May 2020 01:37:14 +0200 [thread overview]
Message-ID: <20200523013714.34559855@lazus.yip> (raw)
In-Reply-To: <20200522175346.GZ1079@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
On Fri, 22 May 2020 13:53:46 -0400
Rich Felker <dalias@libc.org> wrote:
[...]
> > >
> > > OK, I'll inquire with OpenWRT about what's going on here..
> > 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.
> > https://patchwork.ozlabs.org/project/openwrt/patch/20200522153626.1398980-1-lynxis@fe80.eu/
Right, this is related to this bug. musl libc is one of a handful
packages which uses
* git as source
* pinned to a git sha1
* have a PKG_VERSION which looks like a release
So increasing the PKG_VERSION wasn't doing anything to the code.
Best,
lynxis
--
Alexander Couzens
mail: lynxis@fe80.eu
jabber: lynxis@fe80.eu
gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-05-22 23:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 20:22 Harald Welte
2020-05-21 20:40 ` Rich Felker
2020-05-21 21:19 ` Harald Welte
2020-05-21 21:49 ` Rich Felker
2020-05-22 16:50 ` Harald Welte
2020-05-22 17:33 ` Rich Felker
2020-05-22 17:45 ` Hauke Mehrtens
2020-05-22 17:53 ` Rich Felker
2020-05-22 23:37 ` Alexander 'lynxis' Couzens [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200523013714.34559855@lazus.yip \
--to=lynxis@fe80.eu \
--cc=dalias@libc.org \
--cc=hauke@hauke-m.de \
--cc=laforge@gnumonks.org \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).