From: Nick Clifton <nickc@redhat.com>
To: Luis Machado <luis.machado@arm.com>, Paul Eggert <eggert@cs.ucla.edu>
Cc: gdb-patches@sourceware.org, binutils@sourceware.org,
Eli Zaretskii <eliz@gnu.org>, Simon Marchi <simark@simark.ca>
Subject: Re: [PATCH] Disable year 2038 support on 32-bit hosts by default
Date: Wed, 10 Aug 2022 10:41:13 +0100 [thread overview]
Message-ID: <d8268d06-ab01-cdf1-7f51-399503846a1f@redhat.com> (raw)
In-Reply-To: <84fbb332-c6ea-b808-434f-1db99b737df9@arm.com>
Hi Luis,
> Nick, would you know the reason behind binutils not using gnulib?
Originally it was historical - the binutils project was started a
long time before the gnulib project.
These days it is an effort issue - as in it will take a lot of effort
to switch over to using gnulib, and I just do not have the time. But
if someone else is interested in doing the work then I am not against
it.
There may be some technical issue - I seem to remember seeing some
posts in the past about problems with gnulib - but these can probably
be resolved. Also I am not sure about the state of the documentation
for gnulib. If it is minimal, as the gnulib project's web page
suggests, then this is going to hinder adoption into the binutils.
Cheers
Nick
next prev parent reply other threads:[~2022-08-10 9:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 7:51 Luis Machado
2022-08-01 14:08 ` Simon Marchi
2022-08-01 14:17 ` Luis Machado
2022-08-01 15:37 ` Simon Marchi
2022-08-01 15:58 ` Eli Zaretskii
2022-08-02 6:42 ` Luis Machado
2022-08-08 11:34 ` Luis Machado
2022-08-08 11:58 ` Eli Zaretskii
2022-08-08 12:04 ` Luis Machado
2022-08-08 12:38 ` Eli Zaretskii
2022-08-08 17:55 ` Paul Eggert
2022-08-08 18:00 ` Luis Machado
2022-08-08 18:01 ` Luis Machado
2022-08-09 15:49 ` Paul Eggert
2022-08-09 15:59 ` Luis Machado
2022-08-09 16:13 ` Paul Eggert
2022-08-10 9:41 ` Nick Clifton [this message]
2022-08-10 10:14 ` Luis Machado
2022-08-09 16:29 ` Eli Zaretskii
2022-08-09 17:02 ` Paul Eggert
2022-08-10 8:38 ` Alan Modra
2022-08-08 14:51 ` Nick Clifton
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=d8268d06-ab01-cdf1-7f51-399503846a1f@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
--cc=simark@simark.ca \
/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).