From: Janne Blomqvist <blomqvist.janne@gmail.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Thomas Koenig <tkoenig@netcologne.de>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Fortran List <fortran@gcc.gnu.org>,
libstdc++@gcc.gnu.org, bkorb@gnu.org, ibuclaw@gdcproject.org,
Ian Lance Taylor <ian@airs.com>, Jakub Jelinek <jakub@redhat.com>,
cmtice@google.com, simon.marchi@ericsson.com
Subject: Re: Update GCC to autoconf 2.69, automake 1.15.1
Date: Thu, 01 Nov 2018 19:43:00 -0000 [thread overview]
Message-ID: <CAO9iq9Ee1UNfafGhftmDxxPrBj_N+ZPDrs=pZXiEQMN-k=mJQQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1810311703380.31548@digraph.polyomino.org.uk>
On Wed, Oct 31, 2018 at 7:05 PM Joseph Myers <joseph@codesourcery.com>
wrote:
> I've committed this revised patch version
Thank you for taking on this work.
> As noted, my expectation is that libgfortran, libgo, libgomp,
> liboffloadmic, libsanitizer, libphobos maintainers will deal with
> moving those directories to subdir-objects, with any consequent fixes
> needed, to eliminate the automake warnings about subdirectory sources
> without using subdir-objects - and I don't know whether use of ../ in
> source paths in some directories complicates things (if subdir-objects
> would result in attempts to put resulting objects in ../, outside the
> normal build directory for the library) or not.
>
Turned out that for libgfortran, at least, this doesn't seem trivial.
Problem is that we have some of the sources listed relative to $(srcdir) in
Makefile.am, which breaks when enabling subdir-objects. But we can't remove
the $(srcdir) either, becase these sources in question are generated from
m4 sources when --enable-maintainer-mode is enabled, and $(srcdir) is thus
needed so that the generated files will correctly end up in in the source
tree and not the build tree. Gah!
I filed https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87856 to keep track of
this.
--
Janne Blomqvist
next prev parent reply other threads:[~2018-11-01 19:43 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
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 [this message]
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='CAO9iq9Ee1UNfafGhftmDxxPrBj_N+ZPDrs=pZXiEQMN-k=mJQQ@mail.gmail.com' \
--to=blomqvist.janne@gmail.com \
--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 \
--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).