Excellent!
-DrD-
> Hi David
>
> jdk8u-dev build worked perfectly with “—with-code-path” option; no other
> patches were required! Thanks :-)
>
> Regards,
> Manas
>
>
>
>> On 10-Jun-2015, at 10:22 am, Manas Thakur wrote:
>>
>> Okay, I found that I should use “jdk8u-dev”, and not “jdk8u”;
I skimmed it and looks okay to me. Thanks for separating this build work and
avoid interfering the jimage refresh work.
Mandy
> On Jun 15, 2015, at 4:58 PM, Valerie Peng wrote:
>
>
> It seems that the jimage refresh change may still take some time, so we will
> end up removing the makefile
On 19/05/15 01:31, David Holmes wrote:
On 19/05/2015 6:19 AM, Brian Toal wrote:
I'd like to be able to distinguish my openjdk build from others, by
setting java_runtime_name to something that signifies my openjdk
derivative. Is it possible to set java_runtime_name that's used
in .//jdk/src/shar
On Tue, Jun 16, 2015 at 09:28:31AM +0100, Seán Coffey wrote:
> Andreas,
>
> thanks for getting back. Easiest way to reproduce this is probably
> by importing the jdk patch directly :
>
> http://cr.openjdk.java.net/~coffeys/webrev.8080102.jdk9.v2/webrev/
> http://cr.openjdk.java.net/~coffeys/webre
Andreas,
thanks for getting back. Easiest way to reproduce this is probably by
importing the jdk patch directly :
http://cr.openjdk.java.net/~coffeys/webrev.8080102.jdk9.v2/webrev/
http://cr.openjdk.java.net/~coffeys/webrev.8080102.jdk9.v2/webrev/jdk.patch
and then : gmake jdk.crypto.pkcs11
On Mon, Jun 15, 2015 at 02:30:41PM +0100, Seán Coffey wrote:
> Hi,
>
> I had a security library fix reviewed last week [1] and all was ok
> with builds back then. Today, I found that my build is broken and I
> think it's down to the changes introduced from the 8054717 fix.
>
> The build error (sn
