Thanks Goetz! Am Mittwoch, 21. September 2016 schrieb Lindenmaier, Goetz :
Hi,
I uploaded an updated patch queue to my own webrev space: http://cr.openjdk.java.net/~goetz/wr16/s390x_patch_queue/
Vaibhav, you need to apply this to the hs-comp repository.
Best regards, Goetz.
-----Original Message----- From: Volker Simonis [mailto:volker.simonis@gmail.com <javascript:;>] Sent: Dienstag, 20. September 2016 17:38 To: s390x-port-dev@openjdk.java.net <javascript:;>; vaibhavv@us.ibm.com <javascript:;>; Lindenmaier, Goetz <goetz.lindenmaier@sap.com <javascript:;>> Subject: Re: s390x-port-dev post from vaibhavv@us.ibm.com <javascript:;> requires approval
Hi Vaibhav,
thanks a lot for your interest in the s390x port and sorry for the inconvenience. We haven't updated the patch for some weeks and it may be very well possible that it doesn't cleanly apply to the current version any more. But this doesn't mean that we're not working on the port internally.
@Goetz: can you please be so kind to upload a new version of our patch queue?
If your impatient, you could try to sync back the whole jdk9/hs forest to the date when I uploaded the patch queue (around Aug 1st). That should work as I've tested that version before uploading the patches.
That said, I'd like to kindly ask you to subscribe to the s390x-port-dev mailing list at http://mail.openjdk.java.net/mailman/listinfo/s390x-port-dev, otherwise you posts will not be accepted by the list.
Thank you and best regards, Volker
On Tue, Sep 20, 2016 at 3:09 AM, <s390x-port-dev- owner@openjdk.java.net <javascript:;>> wrote:
As list administrator, your authorization is requested for the following mailing list posting:
List: s390x-port-dev@openjdk.java.net <javascript:;> From: vaibhavv@us.ibm.com <javascript:;> Subject: OpenJDK9 build issues for s390x Reason: Post by non-member to a members-only list
At your convenience, visit:
http://mail.openjdk.java.net/mailman/admindb/s390x-port-dev
to approve or deny the request.
---------- Forwarded message ---------- From: Vaibhav Vaingankar <vaibhavv@us.ibm.com <javascript:;>> To: s390x-port-dev@openjdk.java.net <javascript:;> Cc: Cindy Lee <cinderel@ca.ibm.com <javascript:;>>, Amod Borkar <aborkar@us.ibm.com <javascript:;>> Date: Tue, 20 Sep 2016 15:38:55 +0530 Subject: OpenJDK9 build issues for s390x
Hello,
We are trying to build openjdk for s390x. We did face issues while doing the same.
Applying of patch failed After manually making the changes as per the patch build failed
Following are the steps we followed to build openJDK
1. Clone openjdk hs branch
hg clone http://hg.openjdk.java.net/jdk9/hs/ cd hs sh ./get_sources.sh
2. Apply s390x patches
- Download all s390x patches from here. - copy all the .patch files in hs/hotspot/.hg/patches folder - Run following command to apply the patch
cd hs/hotspot hg qpush -a
Note: The patch 9000017-add_defines_shared.patch fails to apply.
Hunk #3 FAILED at 405 1 out of 3 hunks FAILED -- saving rejects to file src/share/vm/utilities/macros.hpp.rej patch failed, rejects left in working dir errors during apply, please fix and refresh 9000017- add_defines_shared.patch We than made the changes manually in the file src/share/vm/utilities/macros.hpp as per the patch.
3. Next, we tried to build using the following commands:
bash ./configure --disable-hotspot-gtest make all
Build failed
gmake[3]: *** No rule to make target `/home/test/hs/jdk/src/java.base/unix/conf/s390x/jvm.cfg', needed by `/home/test/hs/build/linux-s390x-normal-server- release/support/modules_libs/java.base/s390x/jvm.cfg'. Stop. gmake[3]: *** Waiting for unfinished jobs.... gmake[2]: *** [java.base-copy-jdk] Error 1
Please let us know if we are missing anything here.
Regards, Vaibhav
---------- Forwarded message ---------- From: s390x-port-dev-request@openjdk.java.net <javascript:;> To: Cc: Date: Tue, 20 Sep 2016 10:09:11 +0000 Subject: confirm 064fbee247ff69a4e6ba78ad753ee3f97d9cc317 If you reply to this message, keeping the Subject: header intact, Mailman will discard the held message. Do this if the message is spam. If you reply to this message and include an Approved: header with the list password in it, the message will be approved for posting to the list. The Approved: header can also appear in the first line of the body of the reply.