macosx jdk builds failing randomly
David Holmes
david.holmes at oracle.com
Sat Mar 29 00:50:46 UTC 2014
On 29/03/2014 7:00 AM, Pete Brunet wrote:
> Cockpit error - that's what happens when you use --with-target-bits=32
> on macosx. (I also upgraded Java to 8 GA but I doubt that mattered.)
>
> On 3/28/14 12:20 PM, Pete Brunet wrote:
>> It's been two or three weeks since I last built 9 on macosx but I
>> started rebuilding yesterday and am getting random failures in the jdk
>> build:
>>
>> Twice I got this:
>>
>> Compiling 225 files for BUILD_SECURITY
>> Note: Some input files use or override a deprecated API.
>> Note: Recompile with -Xlint:deprecation for details.
>> /usr/bin/printf: illegal option -- s
>> usage: printf format [arguments ...]
>> make[2]: ***
>> [/Users/petebrunet/JDK9/JDK-8034118/jdk9/build/macosx-x86-normal-server-release/jdk/lib/jvm.cfg]
>> Error 1
Your "cockpit error" triggered an actual bug in the code that generates
jvm.cfg in CopyFiles.gmk. The printf on OSX doesn't like text that
starts with -, we need to add the -- flag.
Normally an OSX build would not trigger this logic.
David
>>
>> And twice got this:
>>
>> /Users/petebrunet/JDK9/JDK-8034768/jdk9/jdk/src/macosx/native/sun/awt/LWCToolkit.m:92:
>> warning: ivar name ‘_runnable’ specified on the synthesized property
>> ‘runnable’ not found
>> /Users/petebrunet/JDK9/JDK-8034768/jdk9/jdk/src/macosx/native/sun/awt/LWCToolkit.m:92:
>> error: synthesized property ‘runnable’ must either be named the same as
>> a compatible ivar or must explicitly name an ivar
>> /Users/petebrunet/JDK9/JDK-8034768/jdk9/jdk/src/macosx/native/sun/awt/LWCToolkit.m:
>> In function ‘__doLoadNativeColors_block_invoke_1’:
>> /Users/petebrunet/JDK9/JDK-8034768/jdk9/jdk/src/macosx/native/sun/awt/LWCToolkit.m:288:
>> warning: comparison between signed and unsigned
>> make[2]: ***
>> [/Users/petebrunet/JDK9/JDK-8034768/jdk9/build/macosx-x86-normal-server-release/jdk/objs/libawt_lwawt/LWCToolkit.o]
>> Error 1
>>
>>
>
More information about the build-dev
mailing list