From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27491 invoked by alias); 14 Nov 2014 07:33:33 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 27482 invoked by uid 89); 14 Nov 2014 07:33:32 -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,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mtaout24.012.net.il Received: from mtaout24.012.net.il (HELO mtaout24.012.net.il) (80.179.55.180) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 14 Nov 2014 07:33:30 +0000 Received: from conversion-daemon.mtaout24.012.net.il by mtaout24.012.net.il (HyperSendmail v2007.08) id <0NF000500PMFDN00@mtaout24.012.net.il> for gdb-patches@sourceware.org; Fri, 14 Nov 2014 09:25:57 +0200 (IST) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout24.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NF000PDAPZ93J60@mtaout24.012.net.il>; Fri, 14 Nov 2014 09:25:57 +0200 (IST) Date: Fri, 14 Nov 2014 07:33:00 -0000 From: Eli Zaretskii Subject: Re: gnulib's errno module was imported In-reply-to: <87oasaibe6.fsf@codesourcery.com> To: Yao Qi Cc: gdb-patches@sourceware.org, gregory.0xf0@gmail.com Reply-to: Eli Zaretskii Message-id: <83389mjkxk.fsf@gnu.org> References: <87oasaibe6.fsf@codesourcery.com> X-IsSubscribed: yes X-SW-Source: 2014-11/txt/msg00292.txt.bz2 > From: Yao Qi > CC: > Date: Fri, 14 Nov 2014 13:44:49 +0800 > > I am inclined to back "dirfd" (and "errno") module out. As a result, > gdb will not be compatible with LSB 3.0, but it is just a minor issue to > me. What do you think? Is it possible to back out dirfd, and then add to GDB whatever glue (borrowed from gnulib) that's needed to support LSB 3.0? IOW, can we support LSB 3.0 in our own code, either inspired or stolen from gnulib? IME, gnulib many times includes a lot of overhead in its solutions for problems, while the minimal change to fix the specific problem can be much more lightweight and simple. the question is can we go this way in this case? Thanks.