> On Aug 15, 2021, at 7:31 PM, David Holmes <david.hol...@oracle.com> wrote:
>
> Redirecting to the build-dev alias.
>
> On 15/08/2021 1:22 am, Michael Hall wrote:
>> Seeing the recent comments on build problems I was curious enough to try
>> building on OS/X.
>> I followed the directions here…
>> https://hg.openjdk.java.net/jdk-updates/jdk9u/raw-file/tip/common/doc/building.html
>>
>> <https://hg.openjdk.java.net/jdk-updates/jdk9u/raw-file/tip/common/doc/building.html>
>>
>> <https://hg.openjdk.java.net/jdk-updates/jdk9u/raw-file/tip/common/doc/building.html
>>
>> <https://hg.openjdk.java.net/jdk-updates/jdk9u/raw-file/tip/common/doc/building.html>>
>> I get errors like…
>> === Output from failing command(s) repeated here ===
>> * For target
>> buildtools_buildtools_hotspot_tools_classes__the.BUILD_TOOLS_HOTSPOT_batch:
>> warning: [path] bad path element
>> "/Library/Frameworks/BSF4ooRexx.framework/Classes/bsf4ooRexx-v641-20190830-bin.jar":
>> no such file or directory
>> warning: [path] bad path element
>> "/Applications/OpenOffice.app/Contents/program/classes/ridl.jar": no such
>> file or directory
>> warning: [path] bad path element
>> "/Applications/OpenOffice.app/Contents/program/classes/jurt.jar": no such
>> file or directory
>> warning: [path] bad path element
>> "/Applications/OpenOffice.app/Contents/program/classes/juh.jar": no such
>> file or directory
>> warning: [path] bad path element
>> "/Applications/OpenOffice.app/Contents/program/classes/unoil.jar": no such
>> file or directory
>> warning: [path] bad path element
>> "/Applications/OpenOffice.app/Contents/program": no such file or directory
>> warning: [path] bad path element
>> "/Library/Frameworks/BSF4ooRexx.framework/Classes/bsf4ooRexx-v641-20191126-bin.jar":
>> no such file or directory
>> error: warnings found and -Werror specified
>> 1 error
>> 7 warnings
>
> I would not expect any of the Java based build tools to be picking up any
> default classpath elements from the environment. But I suppose this could be
> a problem if your boot JDK actually refers to wrapper scripts that do set
> such a classpath. I would need to see more details from the build log as to
> what was actually being executed.
It appears to be the OS/X Terminal application that picks it up and adds it to
the environment and the installation process picks it up from the environment
there.
I had deleted the /etc/profile entries that Rony had indicated. Make still
picked up a couple of the errors above. I rebooted and then got a clean build.
Just quitting and restarting Terminal probably would have also worked.
I had just installed the newer BSF4ooRexx version mentioned by Rony. It also
had the export CLASSPATH entries for both BSF4ooRexx and OpenOffice so it
appears that the BSF4ooRexx install is the source for both of those. I removed
them and had been able to build the JDK.
Right after that I got your email. So I uninstalled BSF4ooRexx and reinstalled
to get the /etc/profile export CLASSPATH’s again.
The jdk build was still working.
oops.
I quit and restarted Terminal.
It failed as before. If you are interested in the build.log it is pretty much
as above.
Building target 'images' in configuration 'macosx-x86_64-server-release'
Compiling 1 files for BUILD_TOOLS_HOTSPOT
Compiling 8 files for BUILD_TOOLS_LANGTOOLS
warning: [path] bad path element "/Applications/OpenOffice.app/Contents/lib":
no such file or directory
warning: [path] bad path element
"/Applications/OpenOffice.app/Contents/program/bin": no such file or directory
error: warnings found and -Werror specified
1 error
2 warnings
make[3]: ***
[/Users/mjh/jdk/build/macosx-x86_64-server-release/buildtools/buildtools/hotspot_tools_classes/_the.BUILD_TOOLS_HOTSPOT_batch]
Error 1
make[2]: *** [buildtools-hotspot] Error 2
make[2]: *** Waiting for unfinished jobs....
warning: [path] bad path element "/Applications/OpenOffice.app/Contents/lib":
no such file or directory
warning: [path] bad path element
"/Applications/OpenOffice.app/Contents/program/bin": no such file or directory
error: warnings found and -Werror specified
1 error
2 warnings
make[3]: ***
[/Users/mjh/jdk/build/macosx-x86_64-server-release/buildtools/langtools_tools_classes/_the.BUILD_TOOLS_LANGTOOLS_batch]
Error 1
make[2]: *** [buildtools-langtools] Error 2
ERROR: Build failed for target 'images' in configuration
'macosx-x86_64-server-release' (exit code 2)
If you are considering supporting this and not setting to ignore the
environment I think you might get the not found type errors because the paths
involved include Mac alias’s. You might need to look and see if they are
getting resolved correctly. Normally this might not be a concern for your
builds either.
