From: Paul Eggert <eggert@cs.ucla.edu>
To: Luis Machado <luis.machado@arm.com>
Cc: Simon Marchi <simark@simark.ca>,
binutils@sourceware.org, gdb-patches@sourceware.org,
Nick Clifton <nickc@redhat.com>
Subject: Re: [PATCH] Disable year 2038 support on 32-bit hosts by default
Date: Tue, 9 Aug 2022 09:13:59 -0700 [thread overview]
Message-ID: <2d999f75-b0a5-4298-66eb-486ff474d86b@cs.ucla.edu> (raw)
In-Reply-To: <84fbb332-c6ea-b808-434f-1db99b737df9@arm.com>
On 8/9/22 08:59, Luis Machado wrote:
> that would make BFD use gnulib
Not really. BFD code would not use any Gnulib code as a result of that
patch. It's merely a patch to how BFD is configured, not how it's run.
In other words, no source files under bfd/* change, and libbfd.a
contains no Gnulib code and needs no Gnulib code.
next prev parent reply other threads:[~2022-08-09 16:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 7:51 Luis Machado via Gdb-patches
2022-08-01 14:08 ` Simon Marchi via Gdb-patches
2022-08-01 14:17 ` Luis Machado via Gdb-patches
2022-08-01 15:37 ` Simon Marchi via Gdb-patches
2022-08-01 15:58 ` Eli Zaretskii via Gdb-patches
2022-08-02 6:42 ` Luis Machado via Gdb-patches
2022-08-08 11:34 ` Luis Machado via Gdb-patches
2022-08-08 11:58 ` Eli Zaretskii via Gdb-patches
2022-08-08 12:04 ` Luis Machado via Gdb-patches
2022-08-08 12:38 ` Eli Zaretskii via Gdb-patches
2022-08-08 17:55 ` Paul Eggert
2022-08-08 18:00 ` Luis Machado via Gdb-patches
2022-08-08 18:01 ` Luis Machado via Gdb-patches
2022-08-09 15:49 ` Paul Eggert
2022-08-09 15:59 ` Luis Machado via Gdb-patches
2022-08-09 16:13 ` Paul Eggert [this message]
2022-08-10 9:41 ` Nick Clifton via Gdb-patches
2022-08-10 10:14 ` Luis Machado via Gdb-patches
2022-08-09 16:29 ` Eli Zaretskii via Gdb-patches
2022-08-09 17:02 ` Paul Eggert
2022-08-10 8:38 ` Alan Modra via Gdb-patches
2022-08-08 14:51 ` Nick Clifton via Gdb-patches
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=2d999f75-b0a5-4298-66eb-486ff474d86b@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
--cc=nickc@redhat.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