From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] procps-ng: disable for musl libc
Date: Wed, 03 Jun 2020 06:54:01 +0300 [thread overview]
Message-ID: <877dwo7qjq.fsf@tarshish> (raw)
In-Reply-To: <CAGt4E5sHuMNr38r_adE4Tj2+VmWevAYwyAN9_PSENem4prK0Jw@mail.gmail.com>
Hi Markus,
On Wed, Jun 03 2020, Markus Mayer wrote:
> There is a patch called "procps-ng: disable for musl libc" that was
> applied to 2018.02.x:
>
> https://patchwork.ozlabs.org/project/buildroot/patch/3f2a94307e6c380842726b8158e8ec2e9d24372a.1530616293.git.baruch at tkos.co.il/
>
> This patch does not seem to be in any of the following releases nor is
> it in master.
>
> $ for i in 2018 2019 2020; do for j in 02 05 08 11;do echo "$i/$j";
> git log origin/$i.$j.x | grep 'procps-ng: disable for musl libc';
> done;done
> 2018/02
> procps-ng: disable for musl libc
> 2018/05
> 2018/08
> 2018/11
> 2019/02
> 2019/05
> 2019/08
> 2019/11
> 2020/02
>
> Is this on purpose or should this patch be applied to all releases
> going forward?
This is on purpose.
The commit log you liked to above specifically mentions musl version
1.1.8 in 2018.02.x. Later Buildroot releases include newer versions of
musl that implement the missing fopencookie().
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2020-06-03 3:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 0:02 [Buildroot] procps-ng: disable for musl libc Markus Mayer
2020-06-03 3:54 ` Baruch Siach [this message]
2020-06-03 4:12 ` Markus Mayer
[not found] ` <CAGt4E5svy+bxT=hD_MdR+xjv7uo6UkrAvF+8pq5+KT7_bBLYVg@mail.gmail.com>
2020-06-03 4:19 ` Baruch Siach
2020-06-03 4:27 ` Markus Mayer
2020-06-03 4:35 ` Baruch Siach
2020-06-03 5:07 ` Markus Mayer
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=877dwo7qjq.fsf@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.