misc build snags

David Holmes david.holmes at oracle.com
Thu Dec 20 20:27:50 PST 2012


Kelly,

On 21/12/2012 1:12 PM, Kelly O'Hair wrote:
> On Dec 3, 2012, at 4:11 AM, Doug Lea wrote:
>> 5. On fedora linux I get the following message that is
>> harmless for developer builds but maybe should be better
>> explained somewhere:
>>
>> /usr/bin/chcon: failed to change context of `libjvm.so' to `system_u:object_r:textrel_shlib_t:s0': Operation not supported
>> ERROR: Cannot chcon libjvm.so
>
> Filed 8005377   but I think this may be another thing for the open jdk wiki.
>
> Although, I have been distressed that the makefile rules that do this don't comment why it's necessary and when.

This will jog your memory :)

JDK-6538311 OpenJDK build fails with 'cannot restore segment prot after 
reloc'

>>
>> 6. On solaris, I get various complaints about dtrace,
>> for example:
>>
>> /usr/sfw/bin/gnm: dtrace.o: File format not recognized

Configure is using the wrong tool:

NM:=/usr/sfw/bin/gnm

it should be /usr/ccs/bin/nm

./solaris/makefiles/sparcWorks.make:  NM    = /usr/ccs/bin/nm


>> ld: warning: symbol '__JvmOffsets' has differing types:
>>         (file JvmOffsets.o type=OBJT; file dtrace.o type=FUNC);
>>
>
> I will file 8005378
>
> but I suspect this is a hotspot specific issue, but it needs to be tracked down.

Long standing issue - no investigation AFAICS:

JDK-6890703 dtrace.o causes linker warnings

David



More information about the build-infra-dev mailing list