No rule to make target `images'. Stop. #12
Comments
Hi, I see the following output locally:
Can you write a full sequence how to reproduce the problem (starting with repo checkout)? |
I have a similar problem. |
Thanks for the log, still cannot reproduce locally with clean checkout and This bit looks wrong:
It should be something like this:
Ran it with:
Attaching out.txt. |
On a second thought, can you post your git line endings settings? This is my local output:
|
git config core.autocrlf |
So you have all local files checked out with BTW this also uncovers another issue that top-level build ignores jdk build return status and proceeds with creating ZIP/MSI. Going to fix this. |
I deleted all files and reinstall(git clone). I'm not sure, but I executed this command:
Successful build! |
Re-checked this, scripts in jdk will be broken with Also fixed the bash exit code checking, now Closing the issue. |
Getting similar error while try to build this on windows 10 x64. Setting git
|
Hi, to fix "Bad file permissions" problem you can either run the build as Administrator, or do a |
Thanks, |
@ojdkbuild Reviving the "Bad file permissions" issue. I'm getting the same error as @Draiget (this log contains some debug output I inserted to see what test/file exactly produces the issue):
These are the lines I inserted into generated-config.sh to find out what actually is tested:
No matter how much I chmod in lookaside, I get the same error at this stage, whether I run run.bat from mingw shell, cygwin shell or CMD. No matter which shell I use, When I disable that test (by commenting it out), further down the line an "Access denied" happens (which almost is to be expected given that I disabled the preemptive test for such things, but I don't see how these files should not be accessible...?):
I'm running this on Win10 as user, checked it out after |
Update to my last comment: We now tried to reset Windows10 to a "clean" environment in that we performed the following steps:
Now the build works (or at least: it builds way further than on the last try; at the time of writing this, it is still building). We still don't know which of the above actions led to success, but our best guess about why it did not work is: the company-wide mandatory virus scanner (McAffe) was hindering us, blocking file access outside the user home in some circumstances. So, if this indeed was the root problem, the solution would be moving the build directory into the user home. |
Hi, yes, these Cygwin files permissions are quite brittle. What usually works for me about them:
PS: if you are building jdk8 - there is a major change to build files (dropping all bash and batch scripting and some other changes) that is going to be integrated in some days (it should not affect resulting bits). |
This is not fixing the problem. D:\test\ojdkbuild\tools\cygwin\Cygwin.bat D:\test\ojdkbuild\tools\cygwin64\Cygwin.bat on both i did: kadir@DESKTOP-BNO1KE2:/mnt/d/test$ cd /mnt/d/test/ojdkbuild/lookaside/java-1.8.0-openjdk kadir@DESKTOP-BNO1KE2:/mnt/d/test/ojdkbuild/lookaside/java-1.8.0-openjdk$ stat -c '%a' LICENSE it says 777 for all files kadir@DESKTOP-BNO1KE2:/mnt/d/test/ojdkbuild/lookaside/java-1.8.0-openjdk$ stat -c '%a' * But i entered x64 Native Tools Command Prompt ( Run as Administrator ) hecking for cos in -lm... yes |
If you want just to build OpenJDK 8 for windows and don't need OpenJFX and installer, the following should be the easiest way:
Binaries will go into For customization options see configure call here. Hope this helps. |
When run the step "make images JAVAC_FLAGS=-g LOG=info."
It shows make: *** No rule to make target `images'. Stop.
How to fix it?
The text was updated successfully, but these errors were encountered: