Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
To: Paul Eggert <eggert@cs.ucla.edu>, Nick Clifton <nickc@redhat.com>
Cc: Simon Marchi <simark@simark.ca>,
	binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] Disable year 2038 support on 32-bit hosts by default
Date: Tue, 9 Aug 2022 16:59:30 +0100	[thread overview]
Message-ID: <84fbb332-c6ea-b808-434f-1db99b737df9@arm.com> (raw)
In-Reply-To: <126b860d-0c2c-9fab-a87b-7b97df5ee034@cs.ucla.edu>

On 8/9/22 16:49, Paul Eggert wrote:
> On 8/8/22 11:01, Luis Machado wrote:
>> BFD is left in the dark about the 64-bit time_t support for 32-bit hosts.
> 
> OK, but how about if we fix that by syncing non-Gnulib-using code with Gnulib-using code? This should be relatively easy. Something like the first attached patch, say. If there's still interest in 32-bit binutils this would be a better approach. (If there's not, then we don't have to install any patch. :-)

Sure, but that would make BFD use gnulib, which I don't think is desirable. I don't know why binutils has chosen not to use gnulib, but I'm assuming
the binutils community wouldn't like to pull gnulib code into it without discussing it first. My fix only disables gnulib's use of 64-bit time_t.

Nick, would you know the reason behind binutils not using gnulib?

> 
> PS. While looking into this I noticed a grep portability bug in a couple of 'configure.ac's, fixed in the 2nd attached patch.
> 

Thanks!

> 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. See the 3rd attached file, which is a compressed log of my attempt to build. Here's the first part of the failing output:
> 
>    /bin/sh ../libtool  --tag=CXX   --mode=link gcc -m32 -Wall -pthread -Wno-switch -g -O2       -o gp-archive gp-archive.o ArchiveExp.o libgprofng.la  -L../../zlib -lz
>    libtool: link: gcc -m32 -Wall -pthread -Wno-switch -g -O2 -o gp-archive gp-archive.o ArchiveExp.o  ./.libs/libgprofng.a -L/home/eggert/src/gnu/build/zlib -L/home/eggert/src/gnu/build/libiberty /home/eggert/src/gnu/build/opcodes/.libs/libopcodes.a /home/eggert/src/gnu/build/bfd/.libs/libbfd.a -liberty -lpthread -ldl -lz -pthread
>    /usr/bin/ld: gp-archive.o: in function `er_archive::check_args(int, char**)':
> 
> /home/eggert/src/gnu/build/gprofng/src/../../../binutils-gdb/gprofng/src/gp-archive.cc:573: undefined reference to `operator new(unsigned int)'

Some of the sub-projects within binutils-gdb are C++ now, so it seems this is attempting to build them with a C compiler.

  reply	other threads:[~2022-08-09 16:00 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 [this message]
2022-08-09 16:13                     ` Paul Eggert
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=84fbb332-c6ea-b808-434f-1db99b737df9@arm.com \
    --to=gdb-patches@sourceware.org \
    --cc=binutils@sourceware.org \
    --cc=eggert@cs.ucla.edu \
    --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