Status of all platform builds of jdk7u-osx repos

[Kelly O'Hair]

So how did the jdk changes get integrated without the hotspot changes?
That seems like a process problem. You should NEVER add a dependency on an interface that doesn't exist yet.

Was this a jdk7u-osx issue or a jdk7u-dev issue?

-kto

On Dec 4, 2011, at 1:15 PM, Paul Hohensee wrote:

> Yes, we're missing something in Hotspot.  The fix is in hs23 b07, which is
> being PIT'ed now and will be pushed up to jdk7u-dev Tuesday, if all goes
> well.  We can pull it down to jdk7u-osx as soon as it's pushed to jdk7u-dev.
> 
> Paul
> 
> On 12/4/11 3:44 PM, Kelly O'Hair wrote:
>> FYI...
>> 
>> I ran the jdk7u/jdk7u-osx forest through our internal build system that builds all the platforms
>> plus the Mac.
>> 
>> Only windows builds completed successfully.
>> 
>> On Solaris and Linux, there is some kind of issue with a missing JVM external:
>>     JVM_SetNativeThreadName
>> when building libjava.so. Are we missing something in hotspot?
>> 
>> On the Mac, the builds appeared to complete then die at the last minute with a complaint about
>> options passed into printf. It appears that the Mac does not like the "--" characters being passed
>> in (file make/Defs-internal.gmk in define ReportBuildTimes).
>> 
>> ########################################################################
>> ##### Leaving jdk for target(s) sanity all docs images             #####
>> ########################################################################
>> ##### Build time 00:14:15 jdk for target(s) sanity all docs images #####
>> ########################################################################
>> 
>> /usr/bin/printf: illegal option -- -
>> usage: printf format [arguments ...]
>> make[1]: *** [generic_build_repo_series] Error 1
>> make: *** [build_product_image] Error 2
>> 
>> 
>> -kto
>>