From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 55572 invoked by alias); 11 Oct 2016 20:11:37 -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 55555 invoked by uid 89); 11 Oct 2016 20:11:36 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.8 required=5.0 tests=BAYES_50,FREEMAIL_FROM,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=MILLION, cutting, books, ppl 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 20:11:35 +0000 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1bu3OR-0006tX-JG for crossgcc@sourceware.org; Tue, 11 Oct 2016 22:11:19 +0200 To: crossgcc@sourceware.org From: Grant Edwards Subject: Now problem with make recursion in 1.16.0 Date: Tue, 11 Oct 2016 20:11:00 -0000 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit User-Agent: slrn/1.0.2 (Linux) X-IsSubscribed: yes X-SW-Source: 2016-10/txt/msg00005.txt.bz2 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. Here's the output from my build process: ** removing existing crosstool-NG directory ** unpacking crosstool-ng-1.16.0.tar.bz2 ** copying patches into crosstool-ng ‘patches-1.16.0/ppl/0.11.2/400-fix-redefinition-numeric-limits.patch’ -> ‘crosstool-ng-1.16.0/patches/ppl/0.11.2/400-fix-redefinition-numeric-limits.patch’ ~/nobackup/crosstool/crosstool-ng-1.16.0 ~/nobackup/crosstool ** configuring crosstool-NG with --local checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c [...] configure: overiding all of --prefix and the likes, because --enable-local was set configure: creating ./config.status config.status: creating Makefile ** building crosstool-NG Makefile:115: *** Recursion detected, bailing out.... Stop. Makefile:120: recipe for target 'build' failed make: *** [build] Error 2 Looking at the Makefile, I see this: # Somehow, the new auto-completion for make in the recent distributions # trigger a behavior where our Makefile calls itself recursively, in a # never-ending loop (except on lack of ressources, swap, PIDs...) # Avoid this situation by cutting the recursion short at the first # level. # This has the side effect of only showing the real targets, and hiding our # internal ones. :-) ifneq ($(MAKELEVEL),0) $(error Recursion detected, bailing out...) endif Can somebody explain what "auto-completion" is being referred to? How is immediately failing when recursion is detected supposed to work around the problem? -- Grant Edwards grant.b.edwards Yow! I've read SEVEN at MILLION books!! gmail.com -- For unsubscribe information see http://sourceware.org/lists.html#faq