On 2013-01-13, at 7:17 PM, David Holmes <david.hol...@oracle.com> wrote:
> David, > > I could be mistaken but I thought the use of CXX= was intended as a make > variable to override the value that configure places in the spec.gmk file - > not as a way to force configure to output something to spec.gmk. It's entirely likely that I misunderstood, but I think the output of "sh ./configure -help" could be made less ambiguous. I would ordinarily expect "make help" to inform me of relevant EVs for running make. -------------- Running generated-configure.sh `configure' configures OpenJDK jdk8 to adapt to many kinds of systems. Usage: ./common/autoconf/configure [OPTION]... [VAR=VALUE]... To assign environment variables (e.g., CC, CFLAGS...), specify them as VAR=VALUE. See below for descriptions of some of the useful variables. ... (below) Some influential environment variables: PKG_CONFIG path to pkg-config utility CC C compiler command CFLAGS C compiler flags LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a nonstandard directory <lib dir> LIBS libraries to pass to the linker, e.g. -l<library> CPPFLAGS (Objective) C/C++ preprocessor flags, e.g. -I<include dir> if you have headers in a nonstandard directory <include dir> CXX C++ compiler command CXXFLAGS C++ compiler flags OBJC Objective C compiler command OBJCFLAGS Objective C compiler flags CPP C preprocessor CXXCPP C++ preprocessor XMKMF Path to xmkmf, Makefile generator for X Window System FREETYPE2_CFLAGS C compiler flags for FREETYPE2, overriding pkg-config FREETYPE2_LIBS linker flags for FREETYPE2, overriding pkg-config ALSA_CFLAGS C compiler flags for ALSA, overriding pkg-config ALSA_LIBS linker flags for ALSA, overriding pkg-config Use these variables to override the choices made by `configure' or to help it to find libraries and programs with nonstandard names/locations. --------------