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.

In that case the problem is likely that, due to various level of nested makes, these top-level make variable definitions may not get passed down to all the places that need them. In particular we have already seen several problems where things were not passed to hotspot in a way that hotspot would use.

David

On 12/01/2013 7:01 AM, David Chase wrote:
Problem solved:  /Developer consider harmful, at least on Mountain Lion.
Removing that and using the compilers installed by XCode in /usr/bin did the 
trick.

HOWEVER - it seems dubious to me that configure should ignore the environment 
specification of CXX.
I tried the following,
where /usr/local/bin/g++ is a 4.8.0 compiler that configure will accept if it 
appears first on the path
(this does not lead to a happy build, it merely demonstrates that the compiler 
is acceptable to configure):

(1) sh ./configure CXX=/usr/local/bin/g++
(2) CXX=/usr/local/bin/g++ sh ./configure

I tried (2) because of ambiguous language from sh ./configure -help:

   To assign environment variables (e.g., CC, CFLAGS...), specify them as
   VAR=VALUE.  See below for descriptions of some of the useful variables.

I understand that environment variable bindings precede the command on the 
command line,
but the instructions did not say this explicitly, so I tried it both ways.

I verified that my "sh" is not doing anything non-standard with its environment:

bash-3.2$ CXX=/usr/local/bin/g++ sh -c printenv | grep CXX
CXX=/usr/local/bin/g++

In both cases this was the result of the configure:

Tools summary:
* Boot JDK:       ...
* C Compiler:     i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple 
Inc. build 5658) (LLVM build) version 2336.11.00) (at 
/usr/llvm-gcc-4.2/bin/llvm-gcc-4.2)
* C++ Compiler:   i686-apple-darwin11-llvm-g++-4.2 (GCC) 4.2.1 (Based on Apple 
Inc. build 5658) (LLVM build) version 2336.11.00) (at 
/usr/llvm-gcc-4.2/bin/llvm-g++-4.2)

So, bug?

David

Reply via email to