Building Valhalla/JDK9 on Windows
scolebourne at joda.org
Wed Jan 20 13:09:01 UTC 2016
I've got it to work through two things.
1) hacking generated-configure.sh to hard code CURDIR:
# Save the current directory this script was started from
2) moving the code from the E drive to the C drive, so that freetype,
babun, cygwin and the code are all on the same drive (don't know if this
was needed, as I did it before I tried step 1)
While I can't say for sure, it seemed that once CURDIR was wrong,
everything else failed to resolve correctly against that base. Note that
CURDIR="/c/dev/valhalla/valhalla" did not work, it had to have the extra
thanks for listening
On 20 January 2016 at 08:04, Volker Simonis <volker.simonis at gmail.com>
> Hi Stephen,
> maybe a dump question, but if you do 'dir
> in your cygwin shell, does it work?
> You could also run configure with the '--debug-configure' option.
> Maybe you get some more hints?
> On Tue, Jan 19, 2016 at 10:08 PM, Stephen Colebourne
> <scolebourne at joda.org> wrote:
> > I have just tried building both Valhalla and JDK9 on Windows and failed
> > with the following error during "bash configure":
> > https://java.net/projects/adoptopenjdk/pages/BuildWindows
> > bash configure --with-freetype-src=c:/apps/freetype
> > ...
> > checking if fixpath can be created... yes
> > checking if fixpath.exe works... no
> > Microsoft (R) C/C++ Optimizing Compiler Version 16.00.40219.01 for x64
> > Copyright (C) Microsoft Corporation. All rights reserved.
> > fixpath.c
> > c1 : fatal error C1083: Cannot open source file:
> > No such file or directory
> > configure: error: fixpath did not work!
> > Using Babun shell
> > Windows 7 Professional
> > Have previously successfully compiled OpenJDK (not recently), so have
> > freetype and compilers
> > While it is possible that I might have out of date compilers/freetype,
> > error I'm getting doesn't seem related to anything out of date.
> > Any suggestions?
> > Stephen
More information about the adoption-discuss