From: Alan Modra <amodra@gmail.com>
To: Tom Tromey <tom@tromey.com>
Cc: Alan Modra via Binutils <binutils@sourceware.org>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: @CPP_FOR_BUILD@ problem since binutils-2.38
Date: Wed, 12 Oct 2022 10:10:36 +1030 [thread overview]
Message-ID: <Y0X+9Cb5+Tk0pqgX@squeak.grove.modra.org> (raw)
In-Reply-To: <878rlmqkzr.fsf@tromey.com>
On Tue, Oct 11, 2022 at 12:21:44PM -0600, Tom Tromey wrote:
> >>>>> "Alan" == Alan Modra via Binutils <binutils@sourceware.org> writes:
>
> Alan> To merge with gcc's copy of configure.ac we need to revert changes to
> Alan> configure.ac in the following gcc commits:
> Alan> dc832fb39fc0 2022-08-25
> Alan> fc259b522c0f 2022-06-25
> Alan> Then reapply configure.ac changes in binutils from these binutils
> Alan> commits:
> Alan> 50ad1254d503 2021-01-09
> Alan> bb368aad297f 2022-03-11
> Alan> e5f2f7d901ee 2022-07-26
> Alan> 2cac01e3ffff 2022-09-26
> Alan> Plus copy over gcc's config/ax_cxx_compile_stdcxx.m4, then regenerate
> Alan> configure. configure.ac diff from current binutila shown below.
>
> After this commit I get this when running configure:
>
> ../binutils-gdb/configure: line 5699: ACX_PROG_GDC: command not found
>
> I didn't look but I suppose some .m4 file has to be copied over from gcc
> as well.
Yes, config/acx.m4 needs refreshing. Fixed.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2022-10-11 23:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 4:10 Andrew Goth
2022-10-07 8:42 ` Jan Beulich
2022-10-10 0:43 ` Alan Modra
2022-10-10 6:50 ` Tsukasa OI
2022-10-11 13:03 ` Alan Modra
2022-10-11 18:21 ` Tom Tromey
2022-10-11 23:40 ` Alan Modra [this message]
2022-10-13 4:32 ` Tom Tromey
2022-10-10 10:06 ` 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=Y0X+9Cb5+Tk0pqgX@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=tom@tromey.com \
/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).