On 2013-07-26 21:13, Jonathan Gibbons wrote:
On 07/26/2013 11:58 AM, Tim Bell wrote:
Hi Jon:
Build folk,
I want to writing a script that loops over recent changesets, and
builds JDK each time. One factor to take into account is that I
will occasionally need to rerun the configure script.
On 2013-07-27 07:49, Alan Bateman wrote:
On 26/07/2013 20:38, Mike Duigou wrote:
On Jul 26 2013, at 18:41 , Pete Brunet wrote:
Am doing my first jdk8 build. After reading through the build readme I
didn't see any info on building just jdk and using an import lib. I'm
guessing this is no
Alan, Tim,
I have addressed your comments and as a result - new webrev:
http://cr.openjdk.java.net/~aefimov/8021820/webrev.01
The list of changes:
1. The connection to Oracle site is removed (it's not internal, but
anyway it's better not to rely on availability of external resource in
test).
On 2013-07-31 11:28, David Holmes wrote:
On 31/07/2013 6:46 PM, matchew wrote:
If these variables are deprecated and ignored how is it possible that
java-7 was used for the compilation instead of default one? Anyway to
build
process continues and will check if cacert file was included. If
That was disappointingly slow for sure. Do you have the build time
summary listing?
/Erik
On 2013-08-02 22:26, Pete Brunet wrote:
FWIW I just built 32 bit jdk8 release on 64 bit win 7 with cygwin 1.7.21
on a dual core 8 GB 2.53 GHz Lenovo T500 and the build time was 2:37:45.
That's s feature, not a bug! :)
http://xkcd.com/303/
(Sorry, I couldn't resist)
Cheers,
Mario
Il giorno 02/ago/2013 22:26, Pete Brunet peter.bru...@oracle.com ha
scritto:
FWIW I just built 32 bit jdk8 release on 64 bit win 7 with cygwin 1.7.21
on a dual core 8 GB 2.53 GHz Lenovo T500 and the
I'm building for the first time under the new infrastructure (late to the
party, I know). I appreciate the comprehensive readme page. Here's a list of
minor points of feedback:
The set of repositories and what they contain: need to add nashorn
warn — Default and very quiet: I presume this is
From my experiences there are 3 reasons a compile could be slow:
1. Anti-Virus programs
2. Virtual Machines
3. Network folders
--Max
On 8/6/13 12:48 AM, Pete Brunet wrote:
Hi Erik,
00:05:55 corba
00:09:46 demos
00:15:00 docs
00:18:37 hotspot
00:17:13 images
00:03:32 jaxp
00:11:41 jaxws
Hi Aleksej,
Thanks for the update. I took a look at the revised test, and there are still
some issues. (I didn't look at the build changes.)
1) System-specific resource limits.
I think the biggest issue is resource limits on the number of open files per
process that might vary from system
#1 could be it in my case. I'll report back the next time I build
without that.
On 8/5/13 7:54 PM, Weijun Wang wrote:
From my experiences there are 3 reasons a compile could be slow:
1. Anti-Virus programs
2. Virtual Machines
3. Network folders
--Max
On 8/6/13 12:48 AM, Pete Brunet
10 matches
Mail list logo
