From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9921 invoked by alias); 30 Aug 2013 20:33:29 -0000 Mailing-List: contact libc-ports-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: libc-ports-owner@sourceware.org Received: (qmail 9879 invoked by uid 89); 30 Aug 2013 20:33:27 -0000 Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 30 Aug 2013 20:33:27 +0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RDNS_NONE,SPF_HELO_FAIL autolearn=no version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: relay1.mentorg.com Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58]) by relay1.mentorg.com with esmtp id 1VFVNi-0003NO-G3 from joseph_myers@mentor.com ; Fri, 30 Aug 2013 13:33:22 -0700 Received: from SVR-IES-FEM-01.mgc.mentorg.com ([137.202.0.104]) by SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 30 Aug 2013 13:33:23 -0700 Received: from digraph.polyomino.org.uk (137.202.0.76) by SVR-IES-FEM-01.mgc.mentorg.com (137.202.0.104) with Microsoft SMTP Server id 14.2.247.3; Fri, 30 Aug 2013 21:33:20 +0100 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.76) (envelope-from ) id 1VFVNf-00068R-RF; Fri, 30 Aug 2013 20:33:19 +0000 Date: Fri, 30 Aug 2013 20:33:00 -0000 From: "Joseph S. Myers" To: Carlos O'Donell CC: Mike Frysinger , , Subject: Re: [PATCH v2] hppa: add fanotify_mark In-Reply-To: <5220DB3E.1040609@redhat.com> Message-ID: References: <1377100993-9438-1-git-send-email-vapier@gentoo.org> <1377728809-6729-1-git-send-email-vapier@gentoo.org> <5220DB3E.1040609@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-SW-Source: 2013-08/txt/msg00098.txt.bz2 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