From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org
Subject: Re: [PATCH 2/2] Avoid adding duplicated symbols into static libraries
Date: Wed, 31 Mar 2021 19:35:16 +0530 [thread overview]
Message-ID: <01ebdc66-dda5-a253-32ba-4a9b9e098259@sourceware.org> (raw)
In-Reply-To: <87im571la8.fsf@linux.ibm.com>
On 3/31/21 7:24 PM, Tulio Magno Quites Machado Filho via Libc-alpha wrote:
> I don't think we need to hurry and revert this.
> I'm also looking at this. It has to do with multiarch builds.
>
> I'm sorry for not taking a look at patch 2/2. :-(
Sorry I rushed to push this :)
I posted a fix to patch this up but I think Andreas may have a more
complete fix. Could you please review that one?
https://sourceware.org/pipermail/libc-alpha/2021-March/124602.html
Thanks,
Siddhesh
next prev parent reply other threads:[~2021-03-31 14:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 10:19 [PATCH 0/2] math symbols cleanup Siddhesh Poyarekar
2021-02-11 10:19 ` [PATCH 1/2] Move __isnanf128 to libc.so Siddhesh Poyarekar
2021-02-11 10:27 ` Florian Weimer
2021-02-11 14:14 ` [PATCH v2 " Siddhesh Poyarekar
2021-02-11 16:03 ` Florian Weimer
2021-03-29 13:57 ` Siddhesh Poyarekar
2021-03-29 22:02 ` Tulio Magno Quites Machado Filho
2021-03-30 9:31 ` [COMMITTED] " Siddhesh Poyarekar
2021-02-11 10:19 ` [PATCH 2/2] Avoid adding duplicated symbols into static libraries Siddhesh Poyarekar
2021-03-30 19:47 ` Adhemerval Zanella
2021-03-31 2:57 ` Siddhesh Poyarekar
2021-03-31 13:54 ` Tulio Magno Quites Machado Filho
2021-03-31 14:05 ` Siddhesh Poyarekar [this message]
2021-03-02 6:09 ` [PING][PATCH 0/2] math symbols cleanup Siddhesh Poyarekar
2021-03-22 4:36 ` Siddhesh Poyarekar
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=01ebdc66-dda5-a253-32ba-4a9b9e098259@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=tuliom@ascii.art.br \
/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).