Re: RFR: JDK-8068748: missing US_export_policy.jar in jdk9-b44 is causing compilation errors building jdk9 source code

2015-01-15 Thread Bradford Wetmore
Looks good, thanks for fixing this! Brad On 1/15/2015 3:05 AM, Erik Joelsson wrote: Hello, Please review the open part of this patch, which changes the building of policy jars to happen even if BUILD_CRYPTO is false. Previously these weren't built as there were signed versions of these jars

Re: RFR (XS) 8031064: build_vm_def.sh not working correctly for new build cross compile

2015-01-15 Thread Magnus Ihse Bursie
On 2015-01-15 08:01, David Holmes wrote: If the build-dev guys confirm we already assume bash that is fine. For the rest of the world, we only use bash. For hotspot, we will use bash if called from the top-level Makefile. I can't say anything about what the convention have been for calling t

Re: RFR: JDK-8069041: Bootcycle builds do not work with sjavac

2015-01-15 Thread Magnus Ihse Bursie
On 2015-01-15 10:21, Erik Joelsson wrote: Hello, Please review this small patch which fixes bootcycle-images builds when enabling sjavac. The problem was that the directory where the portfile should be created is never created in the bootcycle-build output directory. I think the best and simp

Re: [aarch64-port-dev ] AARCH64: RFR (XS) 8068927: AARCH64: better handling of aarch64- triples (was RFR: AARCH64: Top-level JDK changes)

2015-01-15 Thread Dean Long
On 1/15/2015 5:41 AM, Magnus Ihse Bursie wrote: On 2015-01-15 00:34, Dean Long wrote: Can I get a review for this? https://bugs.openjdk.java.net/browse/JDK-8068927 http://cr.openjdk.java.net/~dlong/8068927/webrev/ Looks good to me. (However, I'm not a formal reviewer for the aarch64-port pro

Re: RFR: JDK-8069064 Various improvements and fixes in build system

2015-01-15 Thread Volker Simonis
Hi Magnus, I've only had a quick look at your changes but I have a question. When looking at the "make help" I think the relationship between "repo", "target" and "module" is a little unclear. As far as I understand a "target" is an artefact which can be named and build by "make". A "repo" is a

Re: RFR: JDK-8069064 Various improvements and fixes in build system

2015-01-15 Thread Erik Joelsson
Looks good to me. /Erik On 2015-01-15 16:23, Magnus Ihse Bursie wrote: This fix is the result of preparatory work in the build-infra project. It includes: * Remove duplicate detection of comm on Windows * compare.sh enhancements and bug fixes * Do not fail in SetupFoo macros on empty argument

RFR: JDK-8069064 Various improvements and fixes in build system

2015-01-15 Thread Magnus Ihse Bursie
This fix is the result of preparatory work in the build-infra project. It includes: * Remove duplicate detection of comm on Windows * compare.sh enhancements and bug fixes * Do not fail in SetupFoo macros on empty arguments * Minor JavaCompilation enhancements * Makefile warns for unknown contro

Re: RFR: JDK-8069063 More merge errors following JDK-8049367 (Modular Run-Time Images)

2015-01-15 Thread Erik Joelsson
Looks good to me. /Erik On 2015-01-15 15:34, Magnus Ihse Bursie wrote: JDK-8066769 fixed most, but unfortunately not all, of the merge errors following Jigsaw M2. This is a trivial logging failure in Native Compilation. Bug: https://bugs.openjdk.java.net/browse/JDK-8069063 WebRev: http://cr

Re: RFR: JDK-8069057 Make sure configure is run by bash

2015-01-15 Thread Erik Joelsson
Looks good to me. /Erik On 2015-01-15 14:46, Magnus Ihse Bursie wrote: It turns out that our effort to make sure the configure script is run by bash is not fool-proof. The fix is to set CONFIG_SHELL ahead of calling the autoconf script. Thanks to Dean Long for finding out the issue and testi

RFR: JDK-8069063 More merge errors following JDK-8049367 (Modular Run-Time Images)

2015-01-15 Thread Magnus Ihse Bursie
JDK-8066769 fixed most, but unfortunately not all, of the merge errors following Jigsaw M2. This is a trivial logging failure in Native Compilation. Bug: https://bugs.openjdk.java.net/browse/JDK-8069063 WebRev: http://cr.openjdk.java.net/~ihse/JDK-8069063-more-jigsaw-merge-errors/webrev.01 /

RFR: JDK-8069057 Make sure configure is run by bash

2015-01-15 Thread Magnus Ihse Bursie
It turns out that our effort to make sure the configure script is run by bash is not fool-proof. The fix is to set CONFIG_SHELL ahead of calling the autoconf script. Thanks to Dean Long for finding out the issue and testing the patch with dash. Bug: https://bugs.openjdk.java.net/browse/JDK-8

Re: RFR: AARCH64: Top-level JDK changes

2015-01-15 Thread Magnus Ihse Bursie
On 2015-01-14 23:02, Dean Long wrote: On 1/14/2015 5:27 AM, Magnus Ihse Bursie wrote: On 2015-01-13 09:32, Dean Long wrote: On 1/12/2015 3:49 AM, Magnus Ihse Bursie wrote: On 2015-01-12 05:31, Dean Long wrote: I found a small problem with the new config.sub wrapper. It works with the bash sh

Re: [aarch64-port-dev ] AARCH64: RFR (XS) 8068927: AARCH64: better handling of aarch64- triples (was RFR: AARCH64: Top-level JDK changes)

2015-01-15 Thread Magnus Ihse Bursie
On 2015-01-15 00:34, Dean Long wrote: Can I get a review for this? https://bugs.openjdk.java.net/browse/JDK-8068927 http://cr.openjdk.java.net/~dlong/8068927/webrev/ Looks good to me. (However, I'm not a formal reviewer for the aarch64-port project) /Magnus

Re: Problems building jdk8 in Windows - stalls at hotspot, surprisingly continues, refuses to link

2015-01-15 Thread Volker Simonis
On Thu, Jan 15, 2015 at 11:28 AM, Mads Bondo Dydensborg wrote: > Hi Volker > > Thanks a lot for the info. I do not have VS2012, but I do have .NET 4.5.1. > Installing the SP1 solved my problem, but your reference is very handy for > other situations. (And, makes me long for the sane world of Lin

RFR: JDK-8068748: missing US_export_policy.jar in jdk9-b44 is causing compilation errors building jdk9 source code

2015-01-15 Thread Erik Joelsson
Hello, Please review the open part of this patch, which changes the building of policy jars to happen even if BUILD_CRYPTO is false. Previously these weren't built as there were signed versions of these jars, but since we no longer sign them, there is no need to not build them. Bug: https://

RE: Problems building jdk8 in Windows - stalls at hotspot, surprisingly continues, refuses to link

2015-01-15 Thread Mads Bondo Dydensborg
Hi Volker Thanks a lot for the info. I do not have VS2012, but I do have .NET 4.5.1. Installing the SP1 solved my problem, but your reference is very handy for other situations. (And, makes me long for the sane world of Linux). RE the stall : Yes, I have anti-virus software running - this is co

Re: Problems building jdk8 in Windows - stalls at hotspot, surprisingly continues, refuses to link

2015-01-15 Thread Volker Simonis
Hi Mads, The COFF isue is a known problem with VS2010 after installing VS2012 or .NET 4.5.1. There exist various workarounds - just google for "LINK : fatal error LNK1123: failure during conversion to COFF: file invalid". The easiest and fastes solution is to remove the bad version of "cvtres.exe

RFR: JDK-8069041: Bootcycle builds do not work with sjavac

2015-01-15 Thread Erik Joelsson
Hello, Please review this small patch which fixes bootcycle-images builds when enabling sjavac. The problem was that the directory where the portfile should be created is never created in the bootcycle-build output directory. I think the best and simplest solution is to just always create it

RE: Problems building jdk8 in Windows - stalls at hotspot, surprisingly continues, refuses to link

2015-01-15 Thread Mads Bondo Dydensborg
Thanks, Roger, updating Visual Studio Express to service pack 1 seems to allow the build to run to completion. Perhaps this could be suggested in the build guide? The weird "stall" after: Generating jvmtifiles/jvmtiEnvRecommended.cpp Generating jvmtifiles/bytecodeInterpreterWithChecks.cpp Gene

Re: RFR (XS) 8031064: build_vm_def.sh not working correctly for new build cross compile

2015-01-15 Thread Dean Long
On 1/14/2015 11:01 PM, David Holmes wrote: On 15/01/2015 4:40 PM, Dean Long wrote: On 1/14/2015 10:31 PM, David Holmes wrote: Hi Dean, Code reviews don't go to jdk9-dev. Build-infra is not relevant to this either. You only need hotspot-dev for a hotspot build issue (though build-dev might be u