From: Samuel Thibault <samuel.thibault@aquilenet.fr>
To: Guy-Fleury Iteriteka <gfleury@disroot.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 0/4] move some htl symbol into libc
Date: Wed, 2 Nov 2022 17:29:22 +0100 [thread overview]
Message-ID: <20221102162922.iypbyf6yxqfsuzqx@begin> (raw)
In-Reply-To: <20221101222854.r6fp4ad5plj5zhxc@begin>
Samuel Thibault, le mar. 01 nov. 2022 23:28:54 +0100, a ecrit:
> Guy-Fleury Iteriteka via Libc-alpha, le sam. 29 oct. 2022 13:00:26 +0100, a ecrit:
> > pthread_equal is removed from libpthread.so but
> > with the patch for pthread_self is in both libc.so and libpthread.so.
> >
> > this is libpthread.so
> > -------
> > U ___pthread_self@GLIBC_PRIVATE
> > 00006630 t __pthread_self
> > 00006630 t pthread_self
>
> I don't know why that would happen, but you can grep files in htl/ to
> see where that is coming from exactly.
(I meant in the htl/ build tree, to make sure what .o file ends up
defining them)
Samuel
next prev parent reply other threads:[~2022-11-02 16:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 12:00 Guy-Fleury Iteriteka
2022-10-29 12:00 ` [PATCH 1/4] htl: move __pthread-total " Guy-Fleury Iteriteka
2022-10-29 12:00 ` [PATCH 2/4] htl: move ___pthread_self to libc Guy-Fleury Iteriteka
2022-10-29 12:00 ` [PATCH 3/4] htl: move pthread_equal into libc Guy-Fleury Iteriteka
2022-10-30 21:51 ` Samuel Thibault
2022-10-29 12:00 ` [PATCH 4/4] htl: move pthread_self " Guy-Fleury Iteriteka
2022-10-31 7:24 ` Florian Weimer
2022-11-01 19:19 ` Guy-Fleury Iteriteka
2022-11-01 22:28 ` [PATCH 0/4] move some htl symbol " Samuel Thibault
2022-11-02 16:29 ` Samuel Thibault [this message]
2022-11-02 16:36 ` Guy-Fleury Iteriteka
2022-11-03 8:51 ` Guy-Fleury Iteriteka
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=20221102162922.iypbyf6yxqfsuzqx@begin \
--to=samuel.thibault@aquilenet.fr \
--cc=gfleury@disroot.org \
--cc=libc-alpha@sourceware.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).