From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 54198 invoked by alias); 11 Oct 2016 22:14:32 -0000 Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org Received: (qmail 54184 invoked by uid 89); 11 Oct 2016 22:14:31 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=2.6 required=5.0 tests=BAYES_50,FREEMAIL_FROM,KAM_ASCII_DIVIDERS,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=dual, rr, forever, rR X-HELO: blaine.gmane.org Received: from Unknown (HELO blaine.gmane.org) (195.159.176.226) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 11 Oct 2016 22:14:21 +0000 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1bu5JL-0005KU-RH for crossgcc@sourceware.org; Wed, 12 Oct 2016 00:14:11 +0200 To: crossgcc@sourceware.org From: Grant Edwards Subject: Re: Now problem with make recursion in 1.16.0 Date: Tue, 11 Oct 2016 22:14:00 -0000 Message-ID: References: User-Agent: slrn/1.0.2 (Linux) X-IsSubscribed: yes X-SW-Source: 2016-10/txt/msg00006.txt.bz2 On 2016-10-11, Grant Edwards wrote: > I'm trying to rebuild a toolchain using ctng-1.16.0 (updating isn't > really an option at this point in time). > > At some point within the past year, the build worked fine. Now it > fails. The build script, configuration files, and all source files > are under version control. I'm positive they haven't changed. What > probably has changed are the versions of make and autotools that are > running on the build host. The ct-ng Makefile wants to be run with '-R -r' flags. So, it checks the MAKEFLAGS, and if it's not happy it munges them a bit and then calls itself recrusively with the MAKEFLAGS it wants. The problem is that the MAKEFLAGS munging it does doesn't result in MAKEFLAGS that make the child happy, so it would recurse forever if not caught and failed by the MAKELEVEL check. The ct-ng Makefile is checking to see if the MAKEFLAGS contain Rr or -Rr, but there's no guarantee of the order the flag characters are going to show up. In my case, the initial make adds "-Rr" to MAKEFLAGS, but what the child gets is 'rR' which doesn't satisfy it, so the whole thing repeats. I doubt that anybody cares, but here's the patch to Makefile.in that fixes the problem: ------------------------------------------------------------------------------ diff -r -U5 orig/crosstool-ng-1.16.0/Makefile.in fixed/crosstool-ng-1.16.0/Makefile.in --- orig/crosstool-ng-1.16.0/Makefile.in 2012-08-04 16:41:28.000000000 -0500 +++ fixed/crosstool-ng-1.16.0/Makefile.in 2016-10-11 16:42:14.798098680 -0500 @@ -24,11 +24,15 @@ # Note: dual test, because if -R and -r are given on the command line # (who knows?), MAKEFLAGS contains 'Rr' instead of '-Rr', while adding # '-Rr' to MAKEFLAGS adds it literaly ( and does not add 'Rr' ) ifeq ($(filter Rr,$(MAKEFLAGS)),) ifeq ($(filter -Rr,$(MAKEFLAGS)),) +ifeq ($(filter rR,$(MAKEFLAGS)),) +ifeq ($(filter -rR,$(MAKEFLAGS)),) CT_MAKEFLAGS += -Rr +endif # No -rR +endif # No rR endif # No -Rr endif # No Rr # Remove any suffix rules .SUFFIXES: ------------------------------------------------------------------------------ -- Grant Edwards grant.b.edwards Yow! Let me do my TRIBUTE at to FISHNET STOCKINGS ... gmail.com -- For unsubscribe information see http://sourceware.org/lists.html#faq