public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>,
	GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Compat symbols in abilist files
Date: Wed, 19 Apr 2017 02:06:00 -0000	[thread overview]
Message-ID: <cdc6700a-bb47-3749-18be-cdd7e7d32fa8@redhat.com> (raw)
In-Reply-To: <6453f4f9-75b5-68b9-0e6b-22f40aaee599@redhat.com>

On 04/13/2017 09:09 AM, Florian Weimer wrote:
> I've come up with the attached patch to mark compat symbols as such in the abilist files.
> 
> Do we want to do this?  The downside is that when building glibc in certain non-standard configurations, some symbols are not compat symbols anymore (the prime example is probably --enable-obsolete-rpc).  On the other hand, the additional verification is valuable.

I think this is a good idea. We should detect changes in compat symbols as ABI breakage.

The upstream glibc abilist files should be for the default supported configuration.

Downstream distros should patch the abilist to match their configuration changes.

-- 
Cheers,
Carlos.

  parent reply	other threads:[~2017-04-19  2:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13 13:09 Florian Weimer
2017-04-13 13:16 ` Andreas Schwab
2017-04-13 13:20   ` Florian Weimer
2017-04-18 22:18 ` Joseph Myers
2017-04-19  2:10   ` Carlos O'Donell
2017-04-19  9:46     ` Joseph Myers
2017-04-19  2:06 ` Carlos O'Donell [this message]
2017-04-19  7:00   ` Florian Weimer
2021-03-17 20:59 Florian Weimer
2021-03-17 21:21 ` Joseph Myers
2021-03-18 20:25   ` Florian Weimer

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=cdc6700a-bb47-3749-18be-cdd7e7d32fa8@redhat.com \
    --to=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --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).