From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: Mike Frysinger <vapier@gentoo.org>, <libc-ports@sourceware.org>,
<libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] hppa: add fanotify_mark
Date: Fri, 30 Aug 2013 20:33:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1308302029240.22363@digraph.polyomino.org.uk> (raw)
In-Reply-To: <5220DB3E.1040609@redhat.com>
On Fri, 30 Aug 2013, Carlos O'Donell wrote:
> > I'm not entirely sure about the usage of GLIBC_2.19 symbols here.
> > We'd like to backport this so people can use it, but it means we'd
> > be releasing a glibc-2.17/glibc-2.18 with a GLIBC_2.19 symbol in it.
> > But maybe it won't be a big deal since you'd only get that 2.19 ref
> > if you actually used the symbol ?
>
> That's going to be very hard to do without some intense hacking to
> get a 2.17 or 2.18 with a 2.19 symbol. The build system isn't designed
> to allow you to do that?
Backporting a Versions.def addition is trivial.
(Of course if hppa had ABI test baselines, a backport to there would be
needed along with the rest of the changes, but (a) that's just as easy and
(b) that's still on my long list of areas hppa is out of sync with other
ports - such baselines will of course need comparing with past
distribution binaries when added, to detect any ABI bugs introduced over
time.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2013-08-30 20:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 16:03 [PATCH] [RFC] " Mike Frysinger
2013-08-21 16:30 ` Joseph S. Myers
2013-08-26 3:54 ` Mike Frysinger
2013-08-28 22:26 ` [PATCH v2] " Mike Frysinger
2013-08-29 12:15 ` Joseph S. Myers
2013-08-30 0:32 ` Mike Frysinger
2013-08-30 17:49 ` Carlos O'Donell
2013-08-30 20:33 ` Joseph S. Myers [this message]
2013-08-30 20:51 ` Roland McGrath
2013-09-03 16:03 ` Carlos O'Donell
2013-09-18 22:08 ` Roland McGrath
2013-09-03 3:22 ` Mike Frysinger
2013-09-03 3:20 ` [PATCH 1/2 v3] tst-fanotify: new simple test Mike Frysinger
2013-09-03 3:22 ` [PATCH 2/2 v3] hppa: add fanotify_mark Mike Frysinger
2013-09-03 3:23 ` [PATCH 1/2 v3] tst-fanotify: new simple test Mike Frysinger
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=Pine.LNX.4.64.1308302029240.22363@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=vapier@gentoo.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).