From: Thomas Schwinge <thomas@codesourcery.com>
To: Joseph Myers <joseph@codesourcery.com>,
Thomas Koenig <tkoenig@netcologne.de>, <gcc-patches@gcc.gnu.org>
Cc: <redi@gcc.gnu.org>
Subject: Back to requiring "Perl version 5.6.1 (or later)" [PR82856] (was: Update GCC to autoconf 2.69, automake 1.15.1)
Date: Mon, 15 May 2023 21:07:16 +0200 [thread overview]
Message-ID: <87y1lp8lcr.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1810311703380.31548@digraph.polyomino.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]
Hi!
On 2018-10-31T17:04:46+0000, Joseph Myers <joseph@codesourcery.com> wrote:
> On Wed, 31 Oct 2018, Thomas Koenig wrote:
>> Am 31.10.18 um 04:26 schrieb Joseph Myers:
>> > This patch (diffs to generated files omitted below) updates GCC to use
>> > autoconf 2.69 and automake 1.15.1.
>>
>> I think this should fix PR 82856. Maybe you could confirm that this
>> restores automake functionality with perl 5.6.26, and mention the PR
>> in the ChangeLog.
(Perl 5.26, not 5.6.26, is what was meant there; see
<https://git.savannah.gnu.org/cgit/automake.git/commit/?id=13f00eb4493c217269b76614759e452d8302955e>.
I remember well, as I once chased down that patch...)
> At least, the warnings I saw with an older perl version and automake
> 1.11.x are gone when using 1.15.1.
ACK.
> I've committed this revised patch version
> A reference to PR
> bootstrap/82856 has been added. gcc/doc/install.texi has been updated
> to mention the new versions required.
..., but not removed the Perl "5.6.25" 5.26 requirement. OK to push the
attached "Back to requiring "Perl version 5.6.1 (or later)" [PR82856]"?
(Later then to be backported to all relevant release branches, too.)
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
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Back-to-requiring-Perl-version-5.6.1-or-later-PR8285.patch --]
[-- Type: text/x-diff, Size: 1215 bytes --]
From 18153b349eb0062d73e3b2da3a2721dd44884b94 Mon Sep 17 00:00:00 2001
From: Thomas Schwinge <thomas@codesourcery.com>
Date: Mon, 15 May 2023 20:55:11 +0200
Subject: [PATCH] Back to requiring "Perl version 5.6.1 (or later)" [PR82856]
With Subversion r265695 (Git commit 22e052725189a472e4e86ebb6595278a49f4bcdd)
"Update GCC to autoconf 2.69, automake 1.15.1 (PR bootstrap/82856)" we're back
to normal; per Automake 1.15.1 'configure.ac' still "[...] perl 5.6 or better
is required [...]".
PR bootstrap/82856
gcc/
* doc/install.texi (Perl): Back to requiring "Perl version 5.6.1 (or
later)".
---
gcc/doc/install.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index fa91ce1953d..dfab47dac96 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -366,7 +366,7 @@ Necessary (only on some platforms) to untar the source code. Many
systems' @command{tar} programs will also work, only try GNU
@command{tar} if you have problems.
-@item Perl version between 5.6.1 and 5.6.24
+@item Perl version 5.6.1 (or later)
Necessary when targeting Darwin, building @samp{libstdc++},
and not using @option{--disable-symvers}.
--
2.34.1
next prev parent reply other threads:[~2023-05-15 19:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 6:35 Update GCC to autoconf 2.69, automake 1.15.1 Joseph Myers
2018-10-31 8:47 ` Thomas Koenig
2018-10-31 9:14 ` Janne Blomqvist
2018-10-31 10:04 ` Richard Biener
2018-10-31 17:34 ` Joseph Myers
2018-10-31 21:55 ` Ian Lance Taylor
2018-11-01 19:43 ` Janne Blomqvist
2023-05-15 19:07 ` Thomas Schwinge [this message]
2018-10-31 10:09 ` Richard Biener
2018-10-31 14:36 ` Ian Lance Taylor
2018-10-31 14:41 ` Simon Marchi
2018-10-31 17:40 ` Joseph Myers
2018-10-31 17:22 ` Eric Gallager
2018-10-31 18:39 ` Joseph Myers
2018-12-03 3:39 ` Iain Buclaw
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=87y1lp8lcr.fsf@euler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=redi@gcc.gnu.org \
--cc=tkoenig@netcologne.de \
/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).