xattr: Permission denied: build/macosx-aarch64-server-release/jdk/conf/management/jmxremote.password.template

[Vitaly Provodin]

Erik,

thanks a lot!

Terminal did not have the Developer Tools permission - adding it resolves this issue.

Vitaly

> On 26. Jun 2023, at 16:20, erik.joelsson at oracle.com wrote:
> 
> Hello Vitaly,
> This could be a permissions problem with the terminal application you are using. This seems like a common issue if you use something other than the default Terminal application. If so you need to give that application permissions to run "developer tools". It could also be some anti-virus, if you have that installed, that is flagging the file and preventing you from accessing it.
> /Erik
> On 6/23/23 12:54, Vitaly Provodin wrote:
>> Hi all 
>> After migrating to a new macbook I become getting the following error
>> 
>> + make images CONF=macosx-aarch64-server-release
>> Using exact match for CONF=macosx-aarch64-server-release (other matches are possible)
>> Building target 'images' in configuration 'macosx-aarch64-server-release'
>> Compiling up to 1 files for BUILD_TOOLS_HOTSPOT
>> Compiling up to 8 files for BUILD_TOOLS_LANGTOOLS
>> xattr: [Errno 13] Permission denied: ‘~/workspace/openjdk/build/macosx-aarch64-server-release/jdk/conf/management/jmxremote.password.template'
>> make[3]: *** [~/workspace/openjdk/build/macosx-aarch64-server-release/jdk/conf/management/jmxremote.password.template] Error 1
>> make[3]: *** Deleting file `~/workspace/openjdk/build/macosx-aarch64-server-release/jdk/conf/management/jmxremote.password.template'
>> make[2]: *** [jdk.management.agent-copy] Error 2
>> make[2]: *** Waiting for unfinished jobs....
>> 
>> ERROR: Build failed for target 'images' in configuration 'macosx-aarch64-server-release' (exit code 2) 
>> 
>> as far as I understand this file is being generated during make images - not clear why it was not generated in my case… On old macbook it works well.
>> I checked permissions for all dirs. I also launched make on a new clone - with no success…
>> 
>> configure works well. macOS 13.4.1, Xcode 14.3.1
>> Has anybody faced this issue? How it may be resolved?
>> 
>> Thanks in advance for any ideas
>> Vitaly