Add --disable-jfe configure flag to make JFE optional#46
Merged
laijx03 merged 1 commit intoopen64-compiler:developfrom Mar 3, 2026
Merged
Add --disable-jfe configure flag to make JFE optional#46laijx03 merged 1 commit intoopen64-compiler:developfrom
laijx03 merged 1 commit intoopen64-compiler:developfrom
Conversation
The Java Frontend (JFE) and js2mpl require gradle, openjdk-8, cmake, and a correctly set JAVA_HOME — dependencies that many build environments do not have. Currently, configure exits with an error if any of these are missing, blocking the entire build. Add a --disable-jfe flag (following the existing --disable-fortran pattern) that skips JFE dependency checks and excludes jfe/js2mpl from the build. Default behavior is unchanged: JFE is still built unless --disable-jfe is passed. Changes: - configure.ac: Add AC_ARG_ENABLE([jfe]) and AC_SUBST([BUILD_JFE]), wrap JFE checks in an enable_jfe guard - configure: Mirror the configure.ac changes in the generated script - Makefile.in: Add BUILD_JFE variable, gate jfe/js2mpl in GNU4_FE_COMPONENTS and clean targets behind ifeq ($(BUILD_JFE), YES) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
--disable-jfeconfigure flag following the existing--disable-fortranpatternGNU4_FE_COMPONENTSand clean targets behindifeq ($(BUILD_JFE), YES)Motivation
The Java Frontend requires gradle, openjdk-8, cmake, and a correctly configured JAVA_HOME. Currently,
configureexits with an error if any of these are missing, blocking the entire compiler build even for users who only need C/C++ support.This change makes JFE opt-out while preserving full backward compatibility: without
--disable-jfe, the existing checks still run and JFE is built as before.Changes
configure.ac:AC_ARG_ENABLE([jfe]),AC_SUBST([BUILD_JFE]), guard JFE checksconfigure: Mirror configure.ac changes in the pre-generated scriptMakefile.in:BUILD_JFE = @BUILD_JFE@, conditional jfe/js2mpl build and clean targetsTest plan
./configure --disable-jfe— skips JFE checks, builds without jfe/js2mpl./configure(no flag) — existing behavior, JFE checks run, jfe/js2mpl builtmake cleanwith and without JFE — only cleans jfe/js2mpl dirs when enabled🤖 Generated with Claude Code