From: Carlos O'Donell <email@example.com>
Adhemerval Zanella <firstname.lastname@example.org>,
Rich Felker <email@example.com>
Cc: John Scott <firstname.lastname@example.org>
Subject: Re: [musl] Missing _CS_POSIX_V7_THREADS_CFLAGS and Missing _CS_POSIX_V7_THREADS_LDFLAGS
Date: Tue, 8 Mar 2022 15:23:08 -0500 [thread overview]
Message-ID: <email@example.com> (raw)
On 3/8/22 11:32, Adhemerval Zanella wrote:
> On 08/03/2022 11:01, Rich Felker wrote:
>> On Tue, Mar 08, 2022 at 10:52:48AM -0300, Adhemerval Zanella wrote:
>>> On 08/03/2022 10:02, Rich Felker wrote:
>>>> On Tue, Mar 08, 2022 at 06:50:51AM +0000, John Scott wrote:
>>>>> Hi all,
>>>>> Please CC me on replies.
>>>>> It seems like musl is missing these confstr parameters which are
>>>>> necessary to portably get the build flags for building multithreaded
>>>> Yes, we were waiting to add them to pick common numbers that glibc
>>>> would also use. Any idea if they've done that yet? If not I'll ping
>>>> them again, and if they still don't respond I guess we just pick our
>>>> own and let them potentially diverge...
>>> Do you have the initial thread on libc-alpha in hand? I think I missed it.
>>> In any case I would like to not diverge.
>> From 2020:
>> Subject: [RFC][PATCH] * bits/confname.h: Define _CS_POSIX_V7_THREADS_CFLAGS, _CS_POSIX_V7_THREADS_LDFLAGS
>> Message-Id: <firstname.lastname@example.org>
> Thanks, the patch missed some bits but I think the rationale is ok to
> include. If Érico can update the patch I will apply it.
Agreed, there is no reason not to add them.
With libpthread merged into libc (as you noted) this is simpler too.
next prev parent reply other threads:[~2022-03-08 20:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 6:50 John Scott
2022-03-08 13:02 ` Rich Felker
2022-03-08 13:52 ` Adhemerval Zanella
2022-03-08 14:01 ` Rich Felker
2022-03-08 16:32 ` Adhemerval Zanella
2022-03-08 20:23 ` Carlos O'Donell [this message]
2022-03-08 21:22 ` Rich Felker
2022-03-09 0:15 ` Rich Felker
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).