New build system problems
Martin Buchholz
martinrb at google.com
Sat Feb 23 20:05:52 UTC 2013
Hi Erik, Tim, Kelly
Here's a proposed fix for you to review:
http://cr.openjdk.java.net/~martin/webrevs/openjdk8/COMPILER_CHECK_LIST/
Martin
On Fri, Jan 25, 2013 at 3:51 PM, Martin Buchholz <martinrb at google.com>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.
>
> 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.
>
> 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.
>
More information about the build-dev
mailing list