On 2013-01-26 00:51, Martin Buchholz wrote:
I was trying out the shiny new build system.
Problem: configure is not executable - must run bash ./configure
It's traditional for configure scripts to be executable.
I would like configure to be executable too, but openjdk has a tradition
of not allowing executable files in the source repos.
Problem: Your life is hell if you have a non-compiler "cl" command on your
PATH, even on Linux.
checking for cl... /usr/bin/cl
configure: Resolving CC (as /usr/bin/cl) failed, using /usr/bin/cl directly.
with subsequent failure to compile.
This is bad and should definitely be fixed. Filed issue 8006988.
Even if you specify the compiler explicitly, it doesn't help:
CC=/usr/bin/gcc CXX=/usr/bin/g++ bash ./configure
Of course, one can work around this by creating a "tools dir", but excising
the unloved cl from the configure script is tempting and effective.
This should probably also be looked at, but it's a separate issue. Filed
issue 8006989.
/Erik
