public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
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, 9 Aug 2022 10:02:16 -0700	[thread overview]
Message-ID: <ad2071f4-5cca-e2a9-e506-9f7e6b1d2f6e@cs.ucla.edu> (raw)
In-Reply-To: <83y1vxtm7a.fsf@gnu.org>

On 8/9/22 09:29, Eli Zaretskii wrote:
>> Date: Tue, 9 Aug 2022 08:49:53 -0700
>> 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).

Oh, I should make it clear that my failure was with bleeding-edge 
binutils-gdb, commit f56173071020d3e97c98c550ba6264122e5d861d dated Tue 
Aug 9 15:39:02 2022 +0100. My Fedora 36 platform had 
gcc-12.1.1-1.fc36.x86_64 and binutils-2.37-27.fc36.x86_64; I configured 
with CC='gcc -m32' CXX='gcc -m32' to cause the binutils-gdb build to be 
in 32-bit mode.

Hmm, likely that CXX was wrong and I should have used g++ not gcc. 
However, switching to g++ doesn't work either; when I configure it this way:

../binutils-gdb/configure CC='gcc -m32' CXX='g++ -m32'

the build still fails as follows, on both Fedora 36 and Ubuntu 22.04.1 
LTS (which uses GCC 11.2). So there's still something squirrelly going 
on with respect to 32-builds on GNU/Linux, which as I understand it are 
the only builds where these year-2038 fixes are relevant.

   CXX    linux-amd64-ipa.o

../../binutils-gdb/gdbserver/linux-amd64-ipa.cc: In function ‘const 
target_desc* get_ipa_tdesc(int)’:

../../binutils-gdb/gdbserver/linux-amd64-ipa.cc:201:14: error: 
‘amd64_linux_read_description’ was not declared in this scope; did you 
mean ‘i386_linux_read_description’?

   201 |       return amd64_linux_read_description (X86_XSTATE_SSE_MASK, 
true);

       |              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~

       |              i386_linux_read_description

../../binutils-gdb/gdbserver/linux-amd64-ipa.cc: In function ‘void 
initialize_low_tracepoint()’:

../../binutils-gdb/gdbserver/linux-amd64-ipa.cc:282:3: error: 
‘amd64_linux_read_description’ was not declared in this scope; did you 
mean ‘i386_linux_read_description’?

   282 |   amd64_linux_read_description (X86_XSTATE_SSE_MASK, true);

       |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~

       |   i386_linux_read_description


  reply	other threads:[~2022-08-09 17:02 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
2022-08-09 17:02                     ` Paul Eggert [this message]
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=ad2071f4-5cca-e2a9-e506-9f7e6b1d2f6e@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=binutils@sourceware.org \
    --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).