-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8314730: GHA: Drop libfreetype6-dev transitional package in favor of libfreetype-dev #15378
Conversation
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix for the issue looks good and tests pass.
As to removing FreeType as a dependency altogether, I think you'd need to pass --with-freetype=bundled
to the configure
in build-cross-compile.yml
as well. By default, it is set to system
on Linux.
From make/autoconf/lib-freetype.m4
:
FREETYPE_TO_USE=bundled
if test "x$OPENJDK_TARGET_OS" != "xwindows" && \
test "x$OPENJDK_TARGET_OS" != "xmacosx" && \
test "x$OPENJDK_TARGET_OS" != "xaix"; then
FREETYPE_TO_USE=system
fi
I did notice that this is set for the riscv64 build in make/conf/jib-profiles.js
@shipilev This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 8 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
This configuration only exists to verify that the build works. We don't currently use the binaries for anything. Using "bundled" made devkit creation and maintenance simpler. For GHA, I think the builds should be configured the way we expect most users to configure them. On Linux, I think linking to a system installed freetype is more common and desired. |
Integrating to unbreak GHA. /integrate |
Going to push as commit 69d900d.
Your commit was automatically rebased without conflicts. |
I agree, though I have wondered in the past if we should have a build-only run that tests out the non-default options for these (mostly |
Current GHA bootstraps fail for some arches with the incompatibility between libfreetype-dev and libfreetype6-dev. Current RISC-V GHA bootstrap fails due to this conflict.
In both sid, bullseye, jammy, libfreetype6-dev is a transitional package, the alias to libfreetype-dev:
https://packages.debian.org/bullseye/libfreetype6-dev
https://packages.debian.org/sid/libfreetype6-dev
https://packages.ubuntu.com/jammy/libfreetype6-dev
There is therefore no reason to ask for libfreetype6-dev instead of libfreetype-dev.
Additional testing:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15378/head:pull/15378
$ git checkout pull/15378
Update a local copy of the PR:
$ git checkout pull/15378
$ git pull https://git.openjdk.org/jdk.git pull/15378/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15378
View PR using the GUI difftool:
$ git pr show -t 15378
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15378.diff
Webrev
Link to Webrev Comment