bash configure fails on missing javah

2018-01-02 Thread Nir Lisker
I'm trying to build OpenJDK 11 as instructed here: http://hg.openjdk.java.net/jdk/jdk/raw-file/tip/doc/building.html. When executing `bash configure --with-import-modules=jfx_path\rt\build\modular-sdk` (I've build JavaFX) the build fails: checking for java in Boot JDK... ok checking for javac in

Re: bash configure fails on missing javah

2018-01-03 Thread Nir Lisker
On 2018-01-03 05:05, Martin Buchholz wrote: > >> I agree configure should not fail if javah is not found. A high quality >> configure test would first check if javac -h works, then fall back to >> javah >> if that works, regardless of the boot jdk's version. >>

bash configure fails on missing VS tools dir

2018-01-03 Thread Nir Lisker
When trying to build JDK 11 on Windows 10 with VS Express 2013 Update 4 (as stated in the docs - the highest supported version) the build fails: bash configure --with-tools-dir='C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin' ... configure: Found Visual Studio installation at /cygdri

Re: bash configure fails on missing VS tools dir

2018-01-03 Thread Nir Lisker
lease install autoconf and run 'bash autogen.sh' to update the generated files. Error: Cannot continue I downloaded autoconf 2.69. How do I point to it? There is no installation. On Wed, Jan 3, 2018 at 3:24 PM, Erik Joelsson wrote: > Hello Nir, > > On 2018-01-03 13:05, Nir Lisker

Re: bash configure fails on missing VS tools dir

2018-01-03 Thread Nir Lisker
grep -v '^no autoconf in'`" echo "AUTOCONF is ${AUTOCONF}" which prints AUTOCONF is Apologies for the mess. How do I continue? - Nir On Wed, Jan 3, 2018 at 4:54 PM, Erik Joelsson wrote: > Hello Nir, > On 2018-01-03 15:34, Nir Lisker wrote: > > Thanks for the

Re: bash configure fails on missing VS tools dir

2018-01-04 Thread Nir Lisker
now where it installed it. - Nir On Thu, Jan 4, 2018 at 10:29 AM, Erik Joelsson wrote: > Can you run "autoconf --version" on the command line? > > /Erik > > On 2018-01-03 16:33, Nir Lisker wrote: > > Hello Erik, > > I installed autoconf 2.69-3 through cygwin (ind

Re: bash configure fails on missing VS tools dir

2018-01-04 Thread Nir Lisker
10 can work here and is easier to build I'm fine with that. On Thu, Jan 4, 2018 at 12:55 PM, Erik Joelsson wrote: > I think you also need the "Wrapper scripts for autoconf commands". Was a > long time since I did this. > > /Erik > > On 2018-01-04 11:40, Nir Liske

Re: bash configure fails on missing VS tools dir

2018-01-04 Thread Nir Lisker
n/x86_am~1/cl) Hopefully all this would be helpful to someone in the future. On with the rest of the steps... Thanks, Nir On Thu, Jan 4, 2018 at 2:36 PM, Erik Joelsson wrote: > > On 2018-01-04 12:45, Nir Lisker wrote: > > Yes, that did it, autegen.sh completed successfully. Th

Re: bash configure fails on missing VS tools dir

2018-01-04 Thread Nir Lisker
, we should update configure to look for both. > > /Erik > > On 2018-01-04 14:51, Nir Lisker wrote: > > It seems to have accepted vcvarsx86_amd64.bat quietly. Configure > succeeded: > > Tools summary: > * Environment:cygwin version 2.9.0(0.318/5/3) (root at > /c

Re: bash configure fails on missing VS tools dir

2018-01-04 Thread Nir Lisker
Joelsson wrote: > Thanks! I've filed https://bugs.openjdk.java.net/browse/JDK-8194645 > > /Erik > > On 2018-01-04 16:30, Nir Lisker wrote: > > Yeah, make also completed successfully: > > Finished building target 'default (exploded-image)' in configuration &g