You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
openjdk.build/include/top.xml contains a macro <get-platform-arch> which appears to be returning ppc when executing on ppcle, even though the java.os.arch java system property is set correctly to ppcle.
The second match for 'ppc' is true whether the arch is 'ppc' or 'ppcle', so the code to set the property to 'ppc' will be run in both cases. What is puzzling though is that I thought properties in ant were immutable, so the setting the property a second time would have no effect. Perhaps setting a property via a macro in this way means that is not true?
We can test this by reversing the two conditions - check for ppc first and then for ppcle. @Mesbah-Alam - do you have a test environment you could check this theory out on?
The text was updated successfully, but these errors were encountered:
The error was actually that java.os.arch contains ppc64le on this platform, not ppcle, so the check was incorrect. The ant property was immutable as expected.
openjdk.build/include/top.xml contains a macro
<get-platform-arch>
which appears to be returning ppc when executing on ppcle, even though the java.os.arch java system property is set correctly to ppcle.Looking at the code, this may be the issue:
The second match for 'ppc' is true whether the arch is 'ppc' or 'ppcle', so the code to set the property to 'ppc' will be run in both cases. What is puzzling though is that I thought properties in ant were immutable, so the setting the property a second time would have no effect. Perhaps setting a property via a macro in this way means that is not true?
We can test this by reversing the two conditions - check for ppc first and then for ppcle.
@Mesbah-Alam - do you have a test environment you could check this theory out on?
The text was updated successfully, but these errors were encountered: