Date: Fri, 18 Apr 2003 17:07:44 -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: <20030418210744.GC33257@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. I get the same error on all my machines. I re-installed one of my crash boxes from scratch and built the latest versions of the ports that ezm3 depends on, but no luck. It looks like the Makefile in FBSD_SPARC64/gcc gets sucked in when building FBSD_SPARC64/gcc/intl due to being a subdir, which is where it could be getting STAGE_PREFIX from. I got ezm3 it to build with this patch, and the resulting cvsup binary seems to work fine, but it may just be due to removing stuff from the environment as you describe. Jake --- language/modula3/m3compiler/m3cc/gcc/gcc/Makefile.in.orig Fri Apr 18 14:31:46 2003 +++ language/modula3/m3compiler/m3cc/gcc/gcc/Makefile.in Fri Apr 18 14:32:11 2003 @@ -690,8 +690,8 @@ -e 's|%% *|../|g' \ -e 's|%||g' SUBDIR_FLAGS_TO_PASS = $(ORDINARY_FLAGS_TO_PASS) \ - "CC=`echo @quoted_cc_set_by_configure@ | $(PREPEND_DOTDOT_TO_RELATIVE_PATHS)`" \ - "STAGE_PREFIX=`echo @quoted_stage_prefix_set_by_configure@ | $(PREPEND_DOTDOT_TO_RELATIVE_PATHS)`" + "CC=`echo @quoted_cc_set_by_configure@ | $(PREPEND_DOTDOT_TO_RELATIVE_PATHS)`" + # # Lists of files for various purposes.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030418210744.GC33257>