I believe this has been caused by the latest push...

try doing:

make jimages

afaik that should not run the last verification step ;-)

Maurizio

On 02/10/15 20:59, Mani Sarkar wrote:
Hi guys,

I get the below build error half way through build the valhalla build of
OpenJDK:










*ERROR: Failed module access verificationgmake[3]: *** [checkdeps] Error
1gmake[3]: Leaving directory
`<https://adopt-openjdk.ci.cloudbees.com/job/project-valhalla-OpenJDK/ws/valhalla/make
<https://adopt-openjdk.ci.cloudbees.com/job/project-valhalla-OpenJDK/ws/valhalla/make>'>gmake[2]:
*** [verify-modules] Error 1gmake[2]: Leaving directory
`<https://adopt-openjdk.ci.cloudbees.com/job/project-valhalla-OpenJDK/ws/valhalla
<https://adopt-openjdk.ci.cloudbees.com/job/project-valhalla-OpenJDK/ws/valhalla>'>make[1]:
*** [main] Error 1make[1]: Leaving directory
`<https://adopt-openjdk.ci.cloudbees.com/job/project-valhalla-OpenJDK/ws/valhalla
<https://adopt-openjdk.ci.cloudbees.com/job/project-valhalla-OpenJDK/ws/valhalla>'>make:
*** [images] Error 2Build step 'Execute shell' marked build as
failureArchiving artifacts*

Here's the link to the detailed logs -
https://adopt-openjdk.ci.cloudbees.com/view/OpenJDK/job/project-valhalla-OpenJDK/3/consoleFull

Whats the fix to the verify modules issue ? Any flags that would help ?
There are a number of errors like "inaccessible reference:
valhalla.model3.Model3Converter (java.base) ->
com.sun.tools.classfile.AccessFlags (jdk.compiler)".

For your info, I'm building from the
http://hg.openjdk.java.net/valhalla/valhalla/
<http://hg.openjdk.java.net/valhalla/valhalla/corba> repo.

Cheers,
Mani


Reply via email to