Hey Erik,
I was running into warnings in the standard library being treated as
errors with VS 2015, so --disable-warnings-as-errors did the trick :D
The information I remembered turned out to be outdated. I went and
looked at doc/building.html again and found that amber required at least
VS
Hello guys,
I tried the rebaseall and it worked. Tbh, I hadn't really looked into
cygwin that much since I wanted to avoid having PATH conflicts between 3
different versions of tools (one windows, one msys, and one cygwin). I
should have done that right away though since it was really easy to
l... at least
as far as the echo statements go. I also tried using -e on the check
that is not comment out, but with no different results (I'm also using
autoconf 2.69 btw). This is kind of a head scratcher éh. I'm calling it
a night, I think I'll also try taking this up with the msy
tself.
I would try to supply the value for the variable in Unix style
(/j/msys/...) and see if msys converts it correctly then.
/Erik
On 2018-06-11 07:38, jbvernee wrote:
Hello,
I've been trying to build the JDK using an msys2 toolchain, which
seems to be possible according to this
Hello,
I've been trying to build the JDK using an msys2 toolchain, which seems
to be possible according to this thread:
http://mail.openjdk.java.net/pipermail/build-dev/2017-October/019862.html
(although I'm not trying to use gcc, I'm using VS 15). I know it's
advised to use cygwin, but I can
