-
Notifications
You must be signed in to change notification settings - Fork 76
Windows Cygwin Setup Issues #101
Comments
Also to confirm this is what is blocking us from adding Windows binaries to AdoptOpenJDK |
@vsebe Can you update this issue with the current status? Unblocking the Adopt builds is a priority. |
So I can probably update you there. We have confirmed that we are running the same version of cygwin/cygpath. I have tried taking the cygpath binary that you use and sticking it on the machine but had no luck with that either. We also seemed to nail this down to being an issue with server 2012 only as the command runs fine on server 2008r2 |
@gdams Can you test with ie: |
It works fine on our win 2012 R2 Jenkins nodes (internal Jenkins). However, they are different version:
On the AdoptOpenJDK machines:
@gdams Could you try to uninstall the ServerCore WoW feature on the machine and see if it works? |
@vsebe what is the easiest way to do that? |
Just a thought - does
|
It looks like I don't
|
You should be able to set shortnames using fsutil, e.g. |
Looking at https://technet.microsoft.com/en-us/library/cc959352.aspx there's a registry entry Worth validating it's set correctly |
@bletherhead that did it! No need to be in safe mode! |
hmm test build failed... any idea why? |
Is the |
https://ci.adoptopenjdk.net/job/openjdk9_openj9_build_x86-64_windows/ws/openjdk/build/windows-x86_64-normal-server-release/make-support/failure-logs/ (you may need to be logged into our ci to see the files) |
The same failure is encountered when building OpenJDK9:
|
fixpath output sample:
|
any progress with this? |
@gdams On Adopt, I see the OpenJDK builds are running on |
that machine doesn't currently have visual studio 2013 on it. We are also planning to drop it and start building on a pair of 2012 machines |
@vsebe did an experiment compiling OpenJDK on the 2012 machine about 3 comments up (#101 (comment)) which shows that the OJDK build fails on the 2012 machine as well. Has Adopt successfully built OJDK on a 2012 machine? I'm starting to suspect a machine config issue. |
no, this is a brand new machine, It's more than likely a machine config issue :) |
The buildtools targets that requires the new compiler fails (this is not OpenJ9 code).
I just built on an internal Windows 2012R2 Standard machine (no error):
Both machines (the internal Jenkins node and the expternal/AdoptOpenJDK Jenkins node) have been configured using same Ansible playbook.
|
@vsebe Any update on this? |
Log in as Admin, open cygwin bash, work in /cygdrive/c/Users/jenkins/workspace/openj9-openjdk-jdk9 ( (the jenkins user home directory):
However, the jenkins build fails. The working directory is: C:/Users/jenkins/workspace/openjdk9_openj9_build_x86-64_windows/openjdk. |
Path too long. @gdams updated the AdoptOpenJDK jenkins build workspace. '/cygdrive/c/Users/jenkins/jdk9_j9/openjdk/build/windows-x86_64-normal-server-release/images/jdk' found
|
Last 5 builds passed: |
Hi, there is still no Windows version at https://adoptopenjdk.net. Is this intended, if so when a windows release is expected? |
@jmarrero There is a Windows download for Java 9 in the nightly builds https://adoptopenjdk.net/nightly.html?variant=openjdk9-openj9 |
For anyone coming back to this issue later, I cannot confirm the length of the path is definitely the problem, but moving the build workspace to one with a shorter path does appear to have worked for me. |
I am having issues setting up Cygwin on our server 2012r2 machines.
The fundamental issue seems to be with CYGPATH:
This is what your internal machines output (courtesy of @vsebe):
cygpath -s -m -a "C:/Program Files (x86)/Microsoft Visual Studio 12.0" C:/PROGRA~2/MICROS~1.0
This is what our machines output:
cygpath -s -m -a "C:/Program Files (x86)/Microsoft Visual Studio 12.0" C:/Program Files (x86)/MICROS~2.0
This results in a configure error:
'C:/program' is not recognized as an internal or external command,
The text was updated successfully, but these errors were encountered: