Re: jdk8 build failure

Hi Erik, I did a build of the full forest today and all is well. -Pete On 11/15/12 10:47 AM, Pete Brunet wrote: > Erik, I'm sorry. That was bad info. I am building both 7u and 8 and > this must have been from my 7u sanity build. I tried it again on my 8 > directory and there is no INFO: output

Re: Build of jdk-7udev: Error occurred during initialization of VM

I just finished building the full forest and all is well. On 11/15/12 12:17 AM, David Holmes wrote: > Whoops! Sorry Kelly - Missed that line involving the java.lang.invoke. > > David > > On 15/11/2012 3:52 PM, Tim Bell wrote: >> See below for the 'flag day' message related to this, sent to the >>

Re: jdk8 build failure

Erik, I'm sorry. That was bad info. I am building both 7u and 8 and this must have been from my 7u sanity build. I tried it again on my 8 directory and there is no INFO: output. On 11/15/12 10:29 AM, Pete Brunet wrote: > I noticed that it's there for make sanity: > > INFO: ENABLE_FULL_DEBUG_SYM

Re: jdk8 build failure

I noticed that it's there for make sanity: INFO: ENABLE_FULL_DEBUG_SYMBOLS=1 INFO: ZIP_DEBUGINFO_FILES=1 INFO: ENABLE_FULL_DEBUG_SYMBOLS=1 INFO: ZIP_DEBUGINFO_FILES=1 Pete On 11/15/12 10:07 AM, Pete Brunet wrote: > Hi Erik, I had saved my build log. There is no INFO: section and no > occurrence

Re: jdk8 build failure

Hi Erik, I had saved my build log. There is no INFO: section and no occurrences of ZIP_DEBUGINFO_FILES. I'll send you the full log in separate email. -Pete On 11/15/12 9:28 AM, Erik Joelsson wrote: > That is correct, but somehow it is being set since the rule for > sawindbg.map is triggered. So

Re: jdk8 build failure

That is correct, but somehow it is being set since the rule for sawindbg.map is triggered. Somewhere in your log, the state of this variable should be printed like this: INFO: ZIP_DEBUGINFO_FILES=1 Could you see what it says? Or paste that whole section of INFO:? /Erik On 2012-11-15 16:05, P

Re: jdk8 build failure

Hi Erik, I didn't set that. If I understand your note I shouldn't have to set it, i.e. not setting it results in the default of 1 which matches the import jdk setting of 1. Is that right? Pete On 11/15/12 2:40 AM, Erik Joelsson wrote: > Did you set ZIP_DEBUGINFO_FILES=0? The default is 1 and I

Re: Review Request: 8003317: build-infra: Configure fails when current dir is part of a symlink

Looks good. //Fredrik 14 nov 2012 kl. 15:04 skrev Erik Joelsson: > This is a fix for the logic that prevents configure from creating > configurations in undesired directories. If the path to the source root > contains a symlink, the check got fooled and refused to create a > configuration any

Re: Review Request: 8001875: build-infra: We must be able to force static linking of stdc++

Looks good. //Fredrik 14 nov 2012 kl. 12:38 skrev Erik Joelsson: > http://cr.openjdk.java.net/~erikj/8001875/webrev.root.01/ > > > This patch changes the configure paramater --disable-static-link-stdc++ to > the following: > > --w

Re: Review Request: 8003327: build-infra: "/bin/sh: : cannot execute" on solaris

Looks good. //Fredrik 14 nov 2012 kl. 15:25 skrev Erik Joelsson: > This minimal patch fixes a problem with error messages from /bin/sh on > solaris. > > http://cr.openjdk.java.net/~erikj/8003327/webrev.root.01/ > > /Erik

Re: jdk8 build failure

Did you set ZIP_DEBUGINFO_FILES=0? The default is 1 and I can't see any obvious way it would change implicitly. The import jdk you are using had it set to 1 and the import logic expects this setting to match in order to find the files to import. /Erik On 2012-11-15 02:53, Pete Brunet wrote: