From: Gregory Fong <gregory.0xf0@gmail.com>
To: Yao Qi <yao@codesourcery.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: gnulib's errno module was imported
Date: Fri, 14 Nov 2014 08:44:00 -0000 [thread overview]
Message-ID: <CADtm3G6vKUU+-Z38LAnSvG5uPGdGnx_JSkvuKcnRmsNGpsR+Eg@mail.gmail.com> (raw)
In-Reply-To: <87k32yi3ql.fsf@codesourcery.com>
On Fri, Nov 14, 2014 at 12:30 AM, Yao Qi <yao@codesourcery.com> wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> 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?
>
> We can do that but I suspect the value of doing that. How important is
> it to keep GDB head compatible with LSB 3.0 which was released on 2005?
> Maybe distro people are aware of this, but I don't know.
I'm not opposed to something more lightweight than importing gnulib's
dirfd, but RHEL 4 (LSB 3.0) is in extended support through 2017, so I
think there's still value in LSB 3.0 compatibility.
Cheers,
Gregory
next prev parent reply other threads:[~2014-11-14 8:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 5:45 Yao Qi
2014-11-14 7:33 ` Eli Zaretskii
2014-11-14 8:30 ` Yao Qi
2014-11-14 8:44 ` Gregory Fong [this message]
2014-11-14 9:26 ` Eli Zaretskii
2014-11-14 11:29 ` Joel Brobecker
2014-11-14 11:47 ` Pedro Alves
2014-11-14 13:02 ` Yao Qi
2014-11-14 13:21 ` Pedro Alves
2014-11-14 13:54 ` Yao Qi
2014-11-14 14:39 ` Pedro Alves
2014-11-14 15:18 ` Joel Brobecker
2014-11-14 16:01 ` Pedro Alves
2014-11-14 23:08 ` Yao Qi
2014-11-14 14:31 ` Eli Zaretskii
2014-11-14 14:42 ` Pedro Alves
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=CADtm3G6vKUU+-Z38LAnSvG5uPGdGnx_JSkvuKcnRmsNGpsR+Eg@mail.gmail.com \
--to=gregory.0xf0@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.com \
/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