public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Guy-Fleury Iteriteka <gfleury@disroot.org>
To: Zack Weinberg <zack@owlfolio.org>
Cc: libc-alpha@sourceware.org, bug-hurd@gnu.org
Subject: Re: [PATCH 0/3] htl: move __pthtread_total, ___pthread_self, pthread_self
Date: Tue, 03 Jan 2023 20:30:44 +0200	[thread overview]
Message-ID: <CE8F4BBB-5360-4937-A379-5CFFD72AD587@disroot.org> (raw)
In-Reply-To: <ypiklemjmt2r.wl-zack@owlfolio.org>



On January 3, 2023 7:22:20 PM GMT+02:00, Zack Weinberg <zack@owlfolio.org> wrote:
>
>> 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.

https://github.com/flavioc/cross-hurd

We are trying to move htl(hurd pthread library) like it was done for linux nptl.

>
>zw

  parent reply	other threads:[~2023-01-03 18:30 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
2023-01-09 21:59     ` Zack Weinberg
2023-01-03 18:30   ` Guy-Fleury Iteriteka [this message]
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=CE8F4BBB-5360-4937-A379-5CFFD72AD587@disroot.org \
    --to=gfleury@disroot.org \
    --cc=bug-hurd@gnu.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).