Closed JasonBarnabe closed 3 years ago
Hi Jason
I think it causes javah and javac version confiction. For my environment,
arton@nomad:~$ javah -version
javahバージョン"1.8.0_265" # don't worry バージョン is 'version' in Japanese letters
arton@nomad:~$ javac --version
javac 11.0.6
And I got same error. If your case is above, if you could remove javah in your path. Rjb's extconf.rb detects it and uses javac -h instead of javah.
Regards
Thanks for the response. Based on your suggestion, I found that Java openjdk-11 was already included in the image. Removing this first, before installing my preferred version, has made the rjb install consistently succeed.
- run:
name: Remove pre-installed Java (avoid conflicts)
command: sudo apt remove openjdk-11-jdk openjdk-11-jdk-headless openjdk-11-jre openjdk-11-jre-headless
Rjb 1.6.3 build process now checks javac and javah version. It uses javac -h if both versions were different.
In this issue, Jason liked to build with elder version of Java. However it builds with newer version of Java according to the below specification. You should check the warning message output by extconf.rb. For example)
warning: javac and javah version unmatch => javah: 1.8.0, javac: 11.0.6
I have a CircleCI build that's failing to build rjb about half the time. The other half, it works fine.
bundle install
fails with:Environment:
Installing Java:
Full log of rjb install: