From: Thomas Koenig <tkoenig@netcologne.de>
To: Joseph Myers <joseph@codesourcery.com>, gcc-patches@gcc.gnu.org
Cc: fortran@gcc.gnu.org, libstdc++@gcc.gnu.org, bkorb@gnu.org,
ibuclaw@gdcproject.org, ian@airs.com, jakub@redhat.com,
cmtice@google.com, simon.marchi@ericsson.com
Subject: Re: Update GCC to autoconf 2.69, automake 1.15.1
Date: Wed, 31 Oct 2018 08:47:00 -0000 [thread overview]
Message-ID: <b55b056d-30d4-1c3d-48c4-1b1429135347@netcologne.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1810310322420.32487@digraph.polyomino.org.uk>
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.
>
> Makefile.am:48: warning: source file 'caf/single.c' is in a subdirectory,
> Makefile.am:48: but option 'subdir-objects' is disabled
> automake: warning: possible forward-incompatibility.
> automake: At least a source file is in a subdirectory, but the 'subdir-objects'
> automake: automake option hasn't been enabled. For now, the corresponding output
> automake: object file(s) will be placed in the top-level directory. However,
> automake: this behaviour will change in future Automake versions: they
> will
> automake: unconditionally cause object files to be placed in the same subdirectory
> automake: of the corresponding sources.
> automake: You are advised to start using 'subdir-objects' option throughout your
> automake: project, to avoid future incompatibilities.
>
> I think it's best for the relevant maintainers to add subdir-objects
> and do any other associated Makefile.am changes needed. In some cases
> the paths in the warnings involved ../; I don't know if that adds any
> extra complications to the use of subdir-objects.
I'm not an automake expert, but I hope to be able to figure out
what is needed. If not, I guess I'll just ask :-)
What is the plan for the previous branches? Currently, it is necessary
to keep around a special version of automake etc for
--enable-maintainer-mode to work. Backporting a patch which
involves regeneration of files in libgfortran/generated from
the files in libgfortan/m4 would then require keeping two versions
of the relevant tools around, and switching between them.
Would it make sense to backport because of this?
Thanks for your efforts!
Regards
Thomas
next prev parent reply other threads:[~2018-10-31 7:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 6:35 Joseph Myers
2018-10-31 8:47 ` Thomas Koenig [this message]
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 ` Back to requiring "Perl version 5.6.1 (or later)" [PR82856] (was: Update GCC to autoconf 2.69, automake 1.15.1) Thomas Schwinge
2018-10-31 10:09 ` Update GCC to autoconf 2.69, automake 1.15.1 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=b55b056d-30d4-1c3d-48c4-1b1429135347@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=bkorb@gnu.org \
--cc=cmtice@google.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=ian@airs.com \
--cc=ibuclaw@gdcproject.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libstdc++@gcc.gnu.org \
--cc=simon.marchi@ericsson.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).