From: Samuel Thibault <samuel.thibault@gnu.org>
To: Zack Weinberg <zack@owlfolio.org>
Cc: Guy-Fleury Iteriteka <gfleury@disroot.org>,
libc-alpha@sourceware.org, bug-hurd@gnu.org
Subject: Re: [PATCH 0/3] htl: move __pthtread_total, ___pthread_self, pthread_self
Date: Tue, 3 Jan 2023 19:28:54 +0100 [thread overview]
Message-ID: <20230103182854.l6lwhdzmuqobtxu7@begin> (raw)
In-Reply-To: <ypiklemjmt2r.wl-zack@owlfolio.org>
Hello,
Zack Weinberg via Libc-alpha, le mar. 03 janv. 2023 12:22:20 -0500, a ecrit:
> > With this patch i boot up a hurd system with flavio scripts.
>
> Can we get a link to these scripts, please? So we know why they care
> about these symbols being in libc.
He just means that he was able to check the change with a Hurd system
built by flavio scripts. Those scripts work fine without the change, the
change is meant to move pthread symbols from libpthread.so to libc.so,
like was done for NPTL.
Samuel
next prev parent reply other threads:[~2023-01-03 18:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 10:45 Guy-Fleury Iteriteka
2023-01-03 10:45 ` [PATCH 1/3] htl: move __pthtread_total into libc Guy-Fleury Iteriteka
2023-01-03 10:45 ` [PATCH 2/3] htl: move ___pthread_self " Guy-Fleury Iteriteka
2023-01-03 10:45 ` [PATCH 3/3] htl: move pthread_self " Guy-Fleury Iteriteka
2023-01-03 21:50 ` Samuel Thibault
2023-01-03 23:02 ` Samuel Thibault
2023-01-03 17:22 ` [PATCH 0/3] htl: move __pthtread_total, ___pthread_self, pthread_self Zack Weinberg
2023-01-03 18:28 ` Samuel Thibault [this message]
2023-01-09 21:59 ` Zack Weinberg
2023-01-03 18:30 ` Guy-Fleury Iteriteka
2023-01-03 21:50 ` Samuel Thibault
2023-01-04 8:49 ` gfleury
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=20230103182854.l6lwhdzmuqobtxu7@begin \
--to=samuel.thibault@gnu.org \
--cc=bug-hurd@gnu.org \
--cc=gfleury@disroot.org \
--cc=libc-alpha@sourceware.org \
--cc=zack@owlfolio.org \
/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 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 read-only IMAP folder(s) and NNTP newsgroup(s).