Environment-related exec or gmake bug on sparc64

John Polstra jdp at polstra.com
Tue Apr 15 11:48:41 PDT 2003

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
gmake[2]: *** No rule to make target `STAGE_PREFIX'.  Stop.
gmake[2]: Leaving directory
gmake[1]: *** [intl.all] Error 1
gmake[1]: Leaving directory

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?


More information about the freebsd-sparc64 mailing list