From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: luis.machado@arm.com, gdb-patches@sourceware.org,
binutils@sourceware.org, simark@simark.ca
Subject: Re: [PATCH] Disable year 2038 support on 32-bit hosts by default
Date: Tue, 09 Aug 2022 19:29:13 +0300 [thread overview]
Message-ID: <83y1vxtm7a.fsf@gnu.org> (raw)
In-Reply-To: <126b860d-0c2c-9fab-a87b-7b97df5ee034@cs.ucla.edu> (message from Paul Eggert on Tue, 9 Aug 2022 08:49:53 -0700)
> Date: Tue, 9 Aug 2022 08:49:53 -0700
> Cc: gdb-patches@sourceware.org, binutils@sourceware.org,
> Eli Zaretskii <eliz@gnu.org>, Simon Marchi <simark@simark.ca>
> From: Paul Eggert <eggert@cs.ucla.edu>
>
> PPS. I couldn't get a 32-bit version of binutils-gdb to build on Fedora
> x86-64, even without either of the attached patches.
FTR, I regularly do such builds (on native MS-Windows), both the parts
used by GDB when I build GDB, and when I build Binutils themselves. I
never had any trouble (with the caveat that I didn't yet build the
latest Binutils 3.29).
next prev parent reply other threads:[~2022-08-09 16:29 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
2022-08-10 10:14 ` Luis Machado
2022-08-09 16:29 ` Eli Zaretskii [this message]
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=83y1vxtm7a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=binutils@sourceware.org \
--cc=eggert@cs.ucla.edu \
--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).