Date: Wed, 16 Apr 2003 18:25:02 -0400 From: Jake Burkholder <jake@locore.ca> To: John Polstra <jdp@polstra.com> Cc: sparc64@freebsd.org Subject: Re: Environment-related exec or gmake bug on sparc64 Message-ID: <20030416222502.GD16563@locore.ca> In-Reply-To: <XFMail.20030415114837.jdp@polstra.com> References: <XFMail.20030415114837.jdp@polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030416222502.GD16563>