ensure_java() throws error if $JDK/bin/java is not symlinked to $JDK/jre/bin/java
Categories
(Firefox Build System :: Mach Core, defect)
Tracking
(firefox-esr78 unaffected, firefox81 unaffected, firefox82 fixed, firefox83 fixed)
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox81 | --- | unaffected |
firefox82 | --- | fixed |
firefox83 | --- | fixed |
People
(Reporter: mhentges, Assigned: mhentges)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
As reported by :bc, not all linux distros are consistent on how they manage having two paths to java ($JDK/bin/java
and $JDK/jre/bin/java
).
On debian, it's solved by having a symlink between the two.
On fedora, the binary is duplicated and exists in both spots.
Right now, on Fedora, the "java_version == jarsigner_version" check is failing.
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 1•4 years ago
|
||
In the build process, there's two ways that java is used:
- From the path
- From the java-bin-path specified in the mozconfig
Before, to assert that both "java" usages would be consistent, the
implementation assumed that there was only a single "java" binary
per-JDK-version, and all duplicate "binaries" were symlinks to the
original.
However, in Fedora, it has two identical full binaries: one in
$JDK/bin, and one in $JDK/jre/bin. The symlink theory was incorrect.
So instead, we can assert that both "java" usages are consistent
by checking their versions and asserting that they are equivalent.
Pushed by mhentges@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c0db57c7f9f0 ensure java from PATH == java from JDK_BIN_DIR r=rstewart
Comment 3•4 years ago
|
||
bugherder |
Comment 4•4 years ago
|
||
Set release status flags based on info from the regressing bug 1663837
Updated•4 years ago
|
Comment 5•4 years ago
|
||
bugherder uplift |
Updated•4 years ago
|
Description
•