Skip to content
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

jdk24 compiles failing #20746

Closed
pshipton opened this issue Dec 4, 2024 · 11 comments
Closed

jdk24 compiles failing #20746

pshipton opened this issue Dec 4, 2024 · 11 comments
Assignees

Comments

@pshipton
Copy link
Member

pshipton commented Dec 4, 2024

https://openj9-jenkins.osuosl.org/job/Pipeline-OpenJDK-Acceptance/872/

https://openj9-jenkins.osuosl.org/job/Build_JDKnext_x86-64_linux_OpenJDK/800

01:58:17  /usr/local/gcc11/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: /home/jenkins/workspace/Build_JDKnext_x86-64_linux_OpenJDK/build/linux-x86_64-server-release/support/static-native/launcher/main.o: in function `main':
01:58:17  make/src/java.base/share/native/launcher/main.c:101: undefined reference to `JLI_InitArgProcessing'
01:58:17  /usr/local/gcc11/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: make/src/java.base/share/native/launcher/main.c:146: undefined reference to `JLI_List_new'
01:58:17  /usr/local/gcc11/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: make/src/java.base/share/native/launcher/main.c:150: undefined reference to `JLI_StringDup'
01:58:17  /usr/local/gcc11/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: make/src/java.base/share/native/launcher/main.c:150: undefined reference to `JLI_List_add'
01:58:17  /usr/local/gcc11/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: make/src/java.base/share/native/launcher/main.c:152: undefined reference to `JLI_AddArgsFromEnvVar'
01:58:17  /usr/local/gcc11/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: make/src/java.base/share/native/launcher/main.c:164: undefined reference to `JLI_PreprocessArg'
01:58:17  /usr/local/gcc11/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: make/src/java.base/share/native/launcher/main.c:171: undefined reference to `JLI_List_add'
01:58:17  /usr/local/gcc11/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: make/src/java.base/share/native/launcher/main.c:174: undefined reference to `JLI_MemFree'
01:58:17  /usr/local/gcc11/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: make/src/java.base/share/native/launcher/main.c:175: undefined reference to `JLI_MemFree'
01:58:17  /usr/local/gcc11/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: make/src/java.base/share/native/launcher/main.c:180: undefined reference to `JLI_List_add'
01:58:17  /usr/local/gcc11/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: make/src/java.base/share/native/launcher/main.c:184: undefined reference to `JLI_Launch'
01:58:17  /usr/local/gcc11/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: make/src/java.base/share/native/launcher/main.c:166: undefined reference to `JLI_StringDup'
01:58:17  /usr/local/gcc11/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: make/src/java.base/share/native/launcher/main.c:166: undefined reference to `JLI_List_add'
01:58:17  /usr/local/gcc11/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: make/src/java.base/share/native/launcher/main.c:158: undefined reference to `JLI_ReportMessage'
01:58:17  collect2: error: ld returned 1 exit status
@pshipton
Copy link
Member Author

pshipton commented Dec 4, 2024

@JasonFengJ9 fyi

Copy link

github-actions bot commented Dec 4, 2024

Issue Number: 20746
Status: Open
Recommended Components: comp:vm, comp:jclextensions, comp:build

@keithc-ca
Copy link
Contributor

Yes, I noticed that. It's difficult to reproduce locally: twice a build seems to just get stuck (like it's waiting for input from somewhere that's never going to come). Do we need static-launcher, or should we just avoid it?

@keithc-ca
Copy link
Contributor

I see the problem now; in StaticLibs.gmk LIB_FLAGS_FILES is empty and so $(CAT) $(LIB_FLAGS_FILES) will wait forever to read from stdin.

@keithc-ca
Copy link
Contributor

The failure on AIX is different:

[2024-12-04T07:23:23.153Z] StaticLibs.gmk:107: *** Unsupported platform.  Stop.

@pshipton
Copy link
Member Author

pshipton commented Dec 4, 2024

I don't know what static-launcher is.

@keithc-ca
Copy link
Contributor

There are extra rules to build static libraries for use in producing a variant of the java launcher that statically links libjvm.a. OpenJ9 does not (currently?) produce such a static archive so all the static-* targets are not going to work. I have a small fix that seems to address this, but we should discuss whether we want to support static linking.

@pshipton
Copy link
Member Author

pshipton commented Dec 4, 2024

@pshipton
Copy link
Member Author

pshipton commented Dec 4, 2024

@tobi fyi

@keithc-ca
Copy link
Contributor

The problem behind the subject of this issue has been addressed; I created #20764 to discuss whether we should support static launchers with OpenJ9.

Copy link

github-actions bot commented Dec 5, 2024

Issue Number: 20746
Status: Closed
Actual Components: None :(
Actual Assignees: No one :(
PR Assignees: keithc-ca

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants