Hi Erik,
with the small changes proposed in "8026964: Building with an IBM J9
boot jdk requires special settings for BOOT_RTJAR"
https://bugs.openjdk.java.net/browse/JDK-8026964
I could finally successfully build with J9 as bootstrap jdk.
I saw that you already submitted this change so I'm prob
Hi Neil, Steve,
is there an easy way to detect and specify a correct setting for
$(BOOT_RTJAR) if we are using an IBM J9 as bootstrap jdk in the new
build system? With OpenJDK/Oracle based boot jdks $(BOOT_RTJAR) is
simply set to "$BOOT_JDK/jre/lib/rt.jar" but this doesn't work with
IBM J9 because
On Mon, Oct 21, 2013 at 9:02 AM, David Holmes wrote:
> On 19/10/2013 1:15 AM, Volker Simonis wrote:
>>
>> Hi Erik,
>>
>> I had to fix another issue in the JAXWS build
>> (https://bugs.openjdk.java.net/browse/JDK-8026874) but with that I've
>> finally managed to get to the Corba build with a J9 boo
On 19/10/2013 1:50 AM, Erik Joelsson wrote:
Hello Volker,
Building without a -bootclasspath results in the following warning which
is likely why it was added in the first place:
warning: [options] bootstrap class path not set in conjunction with
-source 1.7
Note that we are using the bootstrap
On 19/10/2013 1:15 AM, Volker Simonis wrote:
Hi Erik,
I had to fix another issue in the JAXWS build
(https://bugs.openjdk.java.net/browse/JDK-8026874) but with that I've
finally managed to get to the Corba build with a J9 bootstrap JDK.
With the following small change in BuildCorba.gmk:
-
Hello Volker,
Building without a -bootclasspath results in the following warning which
is likely why it was added in the first place:
warning: [options] bootstrap class path not set in conjunction with
-source 1.7
Note that we are using the bootstrap javac, so it's not the one bundled
with
Hi Erik,
I had to fix another issue in the JAXWS build
(https://bugs.openjdk.java.net/browse/JDK-8026874) but with that I've
finally managed to get to the Corba build with a J9 bootstrap JDK.
With the following small change in BuildCorba.gmk:
- FLAGS:=$(BOOT_JDK_SOURCETARGET) -bootclasspath
On Wed, Oct 16, 2013 at 12:22 PM, Erik Joelsson
wrote:
>
> On 2013-10-15 17:29, Volker Simonis wrote:
>>
>> Hi Erik, Alan,
>>
>> first of all I think this is a good change because it helps porters to
>> build a complete JDK even if the newly build rmic wouldn't run.
>>
>> On the other hand I'm a l
On 15/10/2013 16:29, Volker Simonis wrote:
:
By the way, the main problem why the IBM J9 idlj and rmic didn't work
out of the box were some command line options which were only
supported by the Oracle implementation. It would therefore be very
nice if you could completely remove such options fro
On 16/10/2013 01:04, David Holmes wrote:
I think API restrictions already apply to the sun.tools packages - and
both language and API restrictions apply to other build tools that are
compiled using the boot JDK.
Yes for build tools but not sun.tools.** in general (the change to
sun.tools.tree
On 16/10/2013 11:35, David Holmes wrote:
Ship it! Quickly! :)
+1 looks good to me.
Thanks Erik,
-Chris.
Thanks,
David
On 16/10/2013 8:19 PM, Erik Joelsson wrote:
New webrev: http://cr.openjdk.java.net/~erikj/6604021/webrev.02/
* Changed Node.java as David suggested.
* Added comment sugge
Ship it! Quickly! :)
Thanks,
David
On 16/10/2013 8:19 PM, Erik Joelsson wrote:
New webrev: http://cr.openjdk.java.net/~erikj/6604021/webrev.02/
* Changed Node.java as David suggested.
* Added comment suggested by Martin to Setup.gmk, where the compiler
setup is done. Couldn't think of a better
On 2013-10-15 17:29, Volker Simonis wrote:
Hi Erik, Alan,
first of all I think this is a good change because it helps porters to
build a complete JDK even if the newly build rmic wouldn't run.
On the other hand I'm a little bit concerned if this change still
allows it to bootstrap with a non-O
New webrev: http://cr.openjdk.java.net/~erikj/6604021/webrev.02/
* Changed Node.java as David suggested.
* Added comment suggested by Martin to Setup.gmk, where the compiler
setup is done. Couldn't think of a better place.
* Changed comment in JavaCompilation.
A note on Corba. While the corba
On 16/10/2013 10:02 AM, David Holmes wrote:
Hi Erik,
Many thanks for jumping on this!
On 16/10/2013 12:30 AM, Erik Joelsson wrote:
Currently the RMI stubs in the jdk are built with the newly built rmic
binary at the end of the build. This patch changes that and instead
builds a bootstrap versi
Hi Volker,
On 16/10/2013 1:29 AM, Volker Simonis wrote:
Hi Erik, Alan,
first of all I think this is a good change because it helps porters to
build a complete JDK even if the newly build rmic wouldn't run.
On the other hand I'm a little bit concerned if this change still
allows it to bootstrap
On 16/10/2013 12:40 AM, Alan Bateman wrote:
On 15/10/2013 15:30, Erik Joelsson wrote:
Currently the RMI stubs in the jdk are built with the newly built rmic
binary at the end of the build. This patch changes that and instead
builds a bootstrap version of the rmic classes, much like bootstrap
jav
Hi Erik,
Many thanks for jumping on this!
On 16/10/2013 12:30 AM, Erik Joelsson wrote:
Currently the RMI stubs in the jdk are built with the newly built rmic
binary at the end of the build. This patch changes that and instead
builds a bootstrap version of the rmic classes, much like bootstrap
j
Hi Erik, Alan,
first of all I think this is a good change because it helps porters to
build a complete JDK even if the newly build rmic wouldn't run.
On the other hand I'm a little bit concerned if this change still
allows it to bootstrap with a non-Oracle based bootstrap JDK. I
remember that we
On 2013-10-15 16:40, Alan Bateman wrote:
On 15/10/2013 15:30, Erik Joelsson wrote:
Currently the RMI stubs in the jdk are built with the newly built
rmic binary at the end of the build. This patch changes that and
instead builds a bootstrap version of the rmic classes, much like
bootstrap jav
On 15/10/2013 15:30, Erik Joelsson wrote:
Currently the RMI stubs in the jdk are built with the newly built rmic
binary at the end of the build. This patch changes that and instead
builds a bootstrap version of the rmic classes, much like bootstrap
javac in langtools, which runs on the bootjdk,
Currently the RMI stubs in the jdk are built with the newly built rmic
binary at the end of the build. This patch changes that and instead
builds a bootstrap version of the rmic classes, much like bootstrap
javac in langtools, which runs on the bootjdk, but generates classes for
the new jdk. Th
22 matches
Mail list logo
