From: Alan Modra via Gdb-patches <gdb-patches@sourceware.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: simark@simark.ca, binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] Disable year 2038 support on 32-bit hosts by default
Date: Wed, 10 Aug 2022 18:08:41 +0930 [thread overview]
Message-ID: <YvNukY7h45qraGIG@squeak.grove.modra.org> (raw)
In-Reply-To: <ad2071f4-5cca-e2a9-e506-9f7e6b1d2f6e@cs.ucla.edu>
On Tue, Aug 09, 2022 at 10:02:16AM -0700, Paul Eggert wrote:
> 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'
I regularly build bleeding edge binutils on an x86_64-linux Ubuntu
22.04 box with 32-bit libraries installed using:
CC="gcc -m32" CXX="g++ -m32" \
~/src/binutils-gdb/configure --build=i686-linux --enable-targets=all \
--enable-gold --enable-threads \
--disable-gdb --disable-gdbserver --disable-sim --disable-readline \
--disable-libdecnumber --disable-libbacktrace --disable-gprofng --disable-nls
I'm not sure now why I had --build there rather than --target,
probably something to do with getting more "make check" tests run.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2022-08-10 8:39 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
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 [this message]
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=YvNukY7h45qraGIG@squeak.grove.modra.org \
--to=gdb-patches@sourceware.org \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=eggert@cs.ucla.edu \
--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