From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 101826 invoked by alias); 31 Oct 2018 08:37:39 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 101754 invoked by uid 89); 31 Oct 2018 08:37:38 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,TIME_LIMIT_EXCEEDED autolearn=unavailable version=3.3.2 spammy=H*f:sk:b55b056, H*i:sk:b55b056, H*c:alternative, advised X-HELO: mail-yb1-f181.google.com Received: from mail-yb1-f181.google.com (HELO mail-yb1-f181.google.com) (209.85.219.181) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 31 Oct 2018 08:37:28 +0000 Received: by mail-yb1-f181.google.com with SMTP id v92-v6so6257725ybi.5; Wed, 31 Oct 2018 01:37:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wDbDStDNkl6wk9Drv3czMhUG6VX6gjekbbWxgxdONEk=; b=PPsYlJ+E8R9CpjYxk5marOC8sKcEkDtSqTuYfE69KRaL8iQJdU7+KzkHhy4ynVBTWK 8VJHw65Zd6YJ+x4gC4+ymQb6pM4tfXLH0qGGEycGeFv3kzbrPfihm6CY8ZDm3zvYYs5/ ita0rtvyST/aQmrqQ7W20edKOpzVomP+NYikerLlguaI9edg0ZpxlzwhaqFla2ykWd3z S9e5AEYbgJJxRH7s4S2N86Aom9hu8SNhU6M9dnOEI05zw1BQrpMCRCv2Fb8Qy8u0ZGqQ 7XTBV/aWK6ixYzVw1XvxyS1TOpE8IoGNlYG8eLjbrRejkm3ul4hdaH4R2ll+Vd+UiVLY 7+9Q== MIME-Version: 1.0 References: In-Reply-To: From: Janne Blomqvist Date: Wed, 31 Oct 2018 09:14:00 -0000 Message-ID: Subject: Re: Update GCC to autoconf 2.69, automake 1.15.1 To: Thomas Koenig Cc: "Joseph S. Myers" , GCC Patches , Fortran List , libstdc++@gcc.gnu.org, bkorb@gnu.org, ibuclaw@gdcproject.org, Ian Lance Taylor , Jakub Jelinek , cmtice@google.com, simon.marchi@ericsson.com Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2018-10/txt/msg01997.txt.bz2 On Wed, Oct 31, 2018 at 9:12 AM Thomas Koenig wrote: > > 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 :-) > My understanding is that we need to add 'subdir-objects' to AM_INIT_AUTOMAKE in configure.ac. See e.g. https://autotools.io/automake/options.html (that site is pretty good for describing 'best practices' for modern autotools; there's unfortunately a lot of very outdated autotools tutorials around) 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? > +1 -- Janne Blomqvist