RFR: JDK-8035134: JDK9 unix debug bundle manifest file list issue

Hello, Please review this small fix, correcting the contents of the zipped debuginfo files. They are currently adding the full absolute path name of the debuginfo files to the zip instead of just the filename. Bug: https://bugs.openjdk.java.net/browse/JDK-8035134 Patch inline: diff -r 54dd5b

When will JDK 9 builds move to requiring the boot JDK be JDK 8?

We had problems in jdk9/dev in the last day or so where there were changes pushed to the corba repo that use APIs that are new in JDK 8. This caused problems when building jdk9/dev with a 7uX build as the boot JDK and made it obvious that there are a mix of boot JDKs in use (some people use 7

Re: When will JDK 9 builds move to requiring the boot JDK be JDK 8?

I don't see any reason not to make the switch. I filed this bug back in December: https://bugs.openjdk.java.net/browse/JDK-8030794 /Erik On 2014-04-03 10:43, Alan Bateman wrote: We had problems in jdk9/dev in the last day or so where there were changes pushed to the corba repo that use APIs

make reconfigure?

Every now and then, running make asks me to reconfigure so I call configure again. Recently it is showing ERROR: /space/repos/jdk9/dev/build/macosx-x86_64-normal-server-fastdebug/spec.gmk is not up to date. Please rerun configure! Easiest way to do this is by running 'make reconfigure'.

Re: make reconfigure?

I have also experienced this on Solaris. Haven't investigated it yet though. Filed https://bugs.openjdk.java.net/browse/JDK-8039145 to track it. /Erik On 2014-04-03 11:40, Wang Weijun wrote: Every now and then, running make asks me to reconfigure so I call configure again. Recently it is show

Re: When will JDK 9 builds move to requiring the boot JDK be JDK 8?

On 03/04/2014 09:53, Erik Joelsson wrote: I don't see any reason not to make the switch. I filed this bug back in December: https://bugs.openjdk.java.net/browse/JDK-8030794 Thanks, I can't think of any reason either. So how do we make this happen? Would a mail to jdk9-dev be sufficient to ale

Re: When will JDK 9 builds move to requiring the boot JDK be JDK 8?

FYI. This is already reviewed ;-) http://mail.openjdk.java.net/pipermail/build-dev/2013-December/011406.html -Chris. On 3 Apr 2014, at 11:04, Alan Bateman wrote: > On 03/04/2014 09:53, Erik Joelsson wrote: >> I don't see any reason not to make the switch. I filed this bug back in >> Decem

Re: When will JDK 9 builds move to requiring the boot JDK be JDK 8?

On 03/04/2014 11:12, Chris Hegarty wrote: FYI. This is already reviewed ;-) http://mail.openjdk.java.net/pipermail/build-dev/2013-December/011406.html -Chris. I know but I also replied suggesting that he hold off pending a conclusion on the boot JDK issue. If this is pushed then it's the

Re: When will JDK 9 builds move to requiring the boot JDK be JDK 8?

Don't we also need to modify jprt properties? David On 3/04/2014 8:12 PM, Chris Hegarty wrote: FYI. This is already reviewed ;-) http://mail.openjdk.java.net/pipermail/build-dev/2013-December/011406.html -Chris. On 3 Apr 2014, at 11:04, Alan Bateman wrote: On 03/04/2014 09:53, Erik Joe

Re: When will JDK 9 builds move to requiring the boot JDK be JDK 8?

On 3 Apr 2014, at 11:16, Alan Bateman wrote: > On 03/04/2014 11:12, Chris Hegarty wrote: >> FYI. >> >> This is already reviewed ;-) >> http://mail.openjdk.java.net/pipermail/build-dev/2013-December/011406.html >> >> -Chris. >> >> > I know but I also replied suggesting that he hold off pendi

Re: When will JDK 9 builds move to requiring the boot JDK be JDK 8?

On 03/04/2014 11:17, David Holmes wrote: Don't we also need to modify jprt properties? Which properties need changing David ? We should list them. The strange thing here is that JPRT is already using JDK 8 (b132) as bootstrap. That's how the CORBA build failures passed by me. regards, Sean.

get_source.sh from ssh://host//path

Hi All I'm trying to clone jdk9 from one of my machines to another using ssh. The source was at ssh://host//space/jdk9/dev. Please note the double slash before "space" because it's not under my $HOME. Now I can clone the dev repo but if I go inside and call "sh get_source.sh", it shows tryin

Re: get_source.sh from ssh://host//path

I have had the same problem before and would also appreciate fixing it. /Erik On 2014-04-03 12:47, Weijun Wang wrote: Hi All I'm trying to clone jdk9 from one of my machines to another using ssh. The source was at ssh://host//space/jdk9/dev. Please note the double slash before "space" becaus

Re: When will JDK 9 builds move to requiring the boot JDK be JDK 8?

On 2014-04-03 12:24, Seán Coffey wrote: On 03/04/2014 11:17, David Holmes wrote: Don't we also need to modify jprt properties? Which properties need changing David ? We should list them. The strange thing here is that JPRT is already using JDK 8 (b132) as bootstrap. That's how the CORBA bui

Re: When will JDK 9 builds move to requiring the boot JDK be JDK 8?

As Chris pointed out, we have a patch that's already been reviewed, so making the change is trivial. I do think a bit of a heads up to jdk9-dev is a good idea though. /Erik On 2014-04-03 12:04, Alan Bateman wrote: On 03/04/2014 09:53, Erik Joelsson wrote: I don't see any reason not to make th

Re: [8u20] Request for approval: JDK-8039077: JPRT build configure not setting --with-update-version

Approved. -- Oracle Dalibor Topic | Principal Product Manager Phone: +494089091214 | Mobile:+491737185961 Oracle Java Platform Group ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 Münc

Re: When will JDK 9 builds move to requiring the boot JDK be JDK 8?

The general plan had been to wait until Java 8 was final before switching from JDK 7 to JDK 8. We planned switch internal Oracle build systems to JDK 8 after the April 15th CPU release. However, since there seems to already be a mix of JDK 7 and JDK 8 in use it is probably appropriate to switch

Re: get_source.sh from ssh://host//path

It looks like the problem is at common/bin/hgforest.sh: 222pull_newrepo="`echo ${pull_base}/${i} | sed -e 's@\([^:]/\)//*@\1@g'`" It tries to substitute all repeated slashes into one unless it's after a colon. *Mike*: Is that line really useful or just a beautifier? --Max On Ap

Problem related to building JDK in Windows

Hi , I am trying to build openjk on my windows 7 machine and facing problem as below :- checking for X11/extensions/shape.h... no configure: error: Could not find freetype! You need to build a 64-bit version of freetype. This is not readily available. You can find source code and build instructi

Re: Problem related to building JDK in Windows

Hi Pooja, if you already successfully build freetype according to the steps given in your mail you can simply pass the path of the freetype build output directory (i.e. the one where you find freetype.dll) with the "--with-freetype-lib" option to configure. You should also use "--with-freetype-inc

Re: When will JDK 9 builds move to requiring the boot JDK be JDK 8?

A broader question this issue raises is why are components like corba built using the book JDK rather than the JDK they are a part of? -Joe On 04/03/2014 01:43 AM, Alan Bateman wrote: We had problems in jdk9/dev in the last day or so where there were changes pushed to the corba repo that use

Re: get_source.sh from ssh://host//path

On Apr 3 2014, at 08:23 , Wang Weijun wrote: > It looks like the problem is at > > common/bin/hgforest.sh: > 222 pull_newrepo="`echo ${pull_base}/${i} | sed -e > 's@\([^:]/\)//*@\1@g'`" > > It tries to substitute all repeated slashes into one unless it's after a > colon. > > *Mi

Re: When will JDK 9 builds move to requiring the boot JDK be JDK 8?

On 03/04/2014 16:53, Joe Darcy wrote: A broader question this issue raises is why are components like corba built using the book JDK rather than the JDK they are a part of? As I understand it, the new build compiles the repositories in this order so that it matches the old build. In previous mai

Re: When will JDK 9 builds move to requiring the boot JDK be JDK 8?

On 04/03/2014 09:33 AM, Martin Buchholz wrote: On Thu, Apr 3, 2014 at 8:53 AM, Joe Darcy > wrote: A broader question this issue raises is why are components like corba built using the book JDK rather than the JDK they are a part of? If we're cross-compi

Re: Problem related to building JDK in Windows

Hi Volker , Thanks for the help. But even after giving command as below : - $ ./configure -with-freetype-lib=E:\PoojaJDK8\freetype-2.4.7\freetype-2.4.7\objs\win64\vc2010 --with-freetype-include=E:\PoojaJDK8\freetype-2.4.7\freetype-2.4.7\include\freetype I got below error :- checking for X11/exten

Re: Problem related to building JDK in Windows

If you are building the JDK on WIndows, you probably have Cygwin installed (you won't get very far without it). I suggest you try the Cygwin form of the path instead of the DOS form, and use forward slashes, like this: ./configure --with-freetype-lib=/cygdrive/e/PoojaJDK8/freetype-2.4.7/free

Re: Problem related to building JDK in Windows

Hi Tim, Yeah I have cygwin and I tried with the command you told as below On Fri, Apr 4, 2014 at 12:08 AM, Tim Bell wrote: > If you are building the JDK on WIndows, you probably have Cygwin installed > (you won't get very far without it). > > I suggest you try the Cygwin form of the path inste

Re: Problem related to building JDK in Windows

Hi Tim, Yeah I have cygwin and I tried with the cygwin command you told as below but again I got same error :- $ ./configure --with-freetype-lib=/cygdrive/e/PoojaJDK8/freetype-2.4.7/freetype -2.4.7/objs/win64/vc2010 --with-freetype-include=/cygdrive/e/PoojaJDK8/freetype -2.4.7/freetype-2.4.7/incl

Re: Problem related to building JDK in Windows

Hello Pooja, Have you tried with just: --with-freetype=/cygdrive/e/PoojaJDK8/freetype-2.4.7/freetype-2.4.7 (additionally I think my trial and error got me to put the dll in /cygdrive/e/PoojaJDK8/freetype-2.4.7/freetype-2.4.7/lib) ? For ref, here are the steps I follow when building own: http://lho

Re: When will JDK 9 builds move to requiring the boot JDK be JDK 8?

> > On Thu, Apr 3, 2014 at 8:53 AM, Joe Darcy wrote: >> >>> A broader question this issue raises is why are components like corba >>> built using the book JDK rather than the JDK they are a part of? >> >> As Alan said, for historical reasons only. If you wanted to actually compile corba/jaxp/jaxws