public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org,  Florian Weimer <fw@deneb.enyo.de>
Subject: Re: [PATCH] Revert "linux: Move {f}xstat{at} to compat symbols" for static build
Date: Thu, 21 Jan 2021 18:04:44 +0100	[thread overview]
Message-ID: <87sg6umdar.fsf@igel.home> (raw)
In-Reply-To: <7b8aa936-dd5f-37b6-dfde-718b06be4f61@linaro.org> (Adhemerval Zanella's message of "Thu, 21 Jan 2021 13:41:01 -0300")

On Jan 21 2021, Adhemerval Zanella wrote:

> [PATCH] Revert "linux: Move {f}xstat{at} to compat symbols" for
>  static build
>
> This reverts commit 20b39d59467b0c1d858e89ded8b0cebe55e22f60 for static
> library.  This avoids the need to rebuild the world for the case where
> libstdc++ (and potentially other libraries) are linked to a old glibc.
>
> To avoid requering to provide xstat symbols for newer ABIs (such as
> riscv32) a new LIB_COMPAT macro is added.  It is similar to SHLIB_COMPAT
> but also works for static case (thus evaluating similar to SHLIB_COMPAT
> for both shared and static case).
>
> Checked with a check-abi on all affected ABIs. I also check if the
> static library does contains the xstat symbols.

Ok.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

      reply	other threads:[~2021-01-21 17:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29 19:49 Adhemerval Zanella
2021-01-20 16:52 ` Adhemerval Zanella
2021-01-20 18:03   ` Florian Weimer
2021-01-20 18:28     ` Adhemerval Zanella
2021-01-21  9:21 ` Andreas Schwab
2021-01-21 16:41   ` Adhemerval Zanella
2021-01-21 17:04     ` Andreas Schwab [this message]

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=87sg6umdar.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=fw@deneb.enyo.de \
    --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).