From: Thomas Schwinge <thomas@codesourcery.com>
To: <3246251196ryan@gmail.com>
Cc: Iain Sandoe <iain@sandoe.co.uk>, <gcc@gcc.gnu.org>
Subject: Re: Hints on reconfiguring GCC
Date: Wed, 18 Oct 2023 14:55:18 +0200 [thread overview]
Message-ID: <875y343xah.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <4BD76988-F7CE-4AD1-8802-BAE371D1F9F5@sandoe.co.uk>
Hi Ryan!
In addition to what Iain said:
On 2023-10-15T14:00:47+0100, Iain Sandoe <iain@sandoe.co.uk> wrote:
>> On 15 Oct 2023, at 13:40, R jd <3246251196ryan@gmail.com> wrote:
>> I am part of a team that ensures that GCC is ported for AmigaOS4 and the next generation hardware.
>
> :-)
:-)
>> My question is in regards to the GCC repository (https://github.com/gcc-mirror/gcc) at the time of commit id: 2d280e7eafc086e9df85f50ed1a6526d6a3a204d (GCC 11).
... which is the GCC 11.3 release.
>> I am trying to make a change to libstdc++-v3's crossconfig.m4 file which defines some things that are used in configure.ac which, in turn, generates the configure file.
>>
>> I have built from source AUTOCONF 2.69 and AUTOMAKE 1.15.1 which seem to be the correct versions at the time. I have prepended the binary locations to my PATH.
>>
>> Before making my desired change, if I go into libstdc++-v3 and just run "autoreconf" I see that "configure" has changed. I would have expected no change.
>
> First, I would take a look at what kinds of change have been made to configure - it’s not impossible for things to get out of sync. If it’s just script line numbers, for example, you can probably carry on with your changes.
>
> I tend to use “autoreconf -fv” (but the basic principle is much the same)
I've quickly tried myself, and (as should be) do not see any differences
in the generated files: neither for 'autoconf -f' nor 'autoreconf -f'.
(The latter indeed is what you should use.)
>> For more information you can also see: https://github.com/sba1/adtools/pull/149.
I didn't read that one in detail, but saw mentioned "other patches" -- is
it probably the case that some earlier patch has not properly regenerated
files?
Grüße
Thomas
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
next prev parent reply other threads:[~2023-10-18 12:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPB2dxkMVi=ijhoOo7YVugVPAo3WeOvEpk_FvQMxU7F0BcP2Gw@mail.gmail.com>
2023-10-15 13:00 ` Iain Sandoe
2023-10-18 12:55 ` Thomas Schwinge [this message]
2023-10-18 14:42 ` R jd
2023-10-19 9:30 ` Enable top-level recursive 'autoreconf' (was: Hints on reconfiguring GCC) Thomas Schwinge
2023-10-19 9:57 ` Enable top-level recursive 'autoreconf' Andreas Schwab
2023-10-19 10:42 ` Thomas Schwinge
2023-10-19 23:13 ` Eric Gallager
2023-10-30 1:31 ` Hans-Peter Nilsson
2023-10-20 4:07 ` Alexandre Oliva
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=875y343xah.fsf@euler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=3246251196ryan@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
/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).