From owner-freebsd-sparc64@FreeBSD.ORG Wed Apr 16 15:23:44 2003 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 581EB37B401 for ; Wed, 16 Apr 2003 15:23:44 -0700 (PDT) Received: from k6.locore.ca (k6.locore.ca [198.96.117.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0776943F93 for ; Wed, 16 Apr 2003 15:23:43 -0700 (PDT) (envelope-from jake@k6.locore.ca) Received: from k6.locore.ca (localhost.locore.ca [127.0.0.1]) by k6.locore.ca (8.12.8/8.12.8) with ESMTP id h3GMP3xS023897; Wed, 16 Apr 2003 18:25:03 -0400 (EDT) (envelope-from jake@k6.locore.ca) Received: (from jake@localhost) by k6.locore.ca (8.12.8/8.12.8/Submit) id h3GMP3cd023896; Wed, 16 Apr 2003 18:25:03 -0400 (EDT) Date: Wed, 16 Apr 2003 18:25:02 -0400 From: Jake Burkholder To: John Polstra Message-ID: <20030416222502.GD16563@locore.ca> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i cc: sparc64@freebsd.org Subject: Re: Environment-related exec or gmake bug on sparc64 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Apr 2003 22:23:44 -0000 Apparently, On Tue, Apr 15, 2003 at 11:48:37AM -0700, John Polstra said words to the effect of; > I have the new ezm3 port all ready to commit, including support for > FreeBSD/sparc64. But in testing it on panther.freebsd.org, I've run > into a very strange build failure. It happens during the build of > the gcc-based M3 code generator, and it looks like this: > > [gmake ... lots of compiling in gcc/gcc] > cc -c -DIN_GCC -O -W -Wall -Wwrite-strings -Wstrict-prototypes > -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long > -DHAVE_CONFIG_H -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/config > -I../../gcc/gcc/../include ../../gcc/gcc/ma > in.c -o main.o > (cd intl && gmake all) > gmake[2]: Entering directory > `/s/scratch/jdp/ports/lang/ezm3/work/ezm3-1.1/language/modula3/m3compiler/m3cc/FBSD_S > PARC64/gcc/in > tl' > gmake[2]: *** No rule to make target `STAGE_PREFIX'. Stop. > gmake[2]: Leaving directory > `/s/scratch/jdp/ports/lang/ezm3/work/ezm3-1.1/language/modula3/m3compiler/m3cc/FBSD_S > PARC64/gcc/int > l' > gmake[1]: *** [intl.all] Error 1 > gmake[1]: Leaving directory > `/s/scratch/jdp/ports/lang/ezm3/work/ezm3-1.1/language/modula3/m3compiler/m3cc/FBSD_S > PARC64/gcc' > > When I build this portion manually (i.e., outside of the ports > system) it works OK. Furthermore, the Makefile in question doesn't > even contain the string "STAGE_PREFIX" which it is complaining > about, and it doesn't have any include directives in it either. > > After a lot of flailing around, I found that success or failure > depends on the size of what is in the environment. If I prune the > environment down to 37 variables / 939 characters, it works. If I > add the setting "x=y" (arbitrary) to the environment, it fails. > > Has anybody else seen signs of this problem? I haven't seen anything like this, no. How can I reproduce it? Has the port been committed? (kris mentioned it had). I looked in /s/scratch/jdp on panther but I get a different error trying to build ezm3 from that. Jake