On Wed, 23 Oct 2024 01:40:59 GMT, Jiangli Zhou <jian...@openjdk.org> wrote:

> > When trying to sort out the LDFLAGS issues, it turned out that I could not 
> > run the linux launcher at all, not even when checking out older commits of 
> > this PR. I am almost at a loss here; I assume that this worked when I 
> > created this PR (even though I only did ad hoc testing at the time), and 
> > I'm not sure if my testing then was inadequate or if something else has 
> > changed during that time with my environment.
> > I'm trying to retrace my steps in how I got to this branch, but I have 
> > unfortunately deleted much of the intermediate steps.
> > @jianglizhou Can you check if you can build and run a simple 
> > HelloWorld.java with the static launcher in this PR on linux? 
> > `images/static-jdk/bin/java --version` works for me, but not 
> > `images/static-jdk/bin/java HelloWorld.java`, which fails with an error 
> > that indicates it cannot locate the jimage library.
> 
> @magicus I just noticed your above notes now (I'm been chasing an unrelated 
> long G1 Evacuation Pause issue). I'll test your changes tomorrow. Will update 
> you in the thread.

Sorry for the delay. I finally found some time to look into this today. Running 
the latest `static-jdk` `bin/java` built from your branch fails for me as well:


$ bin/java
Error: failed , because bin/java: undefined symbol: JNI_CreateJavaVM


I only took a quick look, but I think this looks like 
https://bugs.openjdk.org/browse/JDK-8339522 that I filed in September.


$ nm bin/java | grep JNI_CreateJavaVM
000000000162733c t JNI_CreateJavaVM
0000000001626e75 t _ZL22JNI_CreateJavaVM_innerPP7JavaVM_PPvS2_
jianglizhou@leia:~/github/jdk_pull_20837/build/linux-x86_64-server-slowdebug/images/static-jdk$
 nm -D bin/java | grep JNI_CreateJavaVM


The VM dynamic symbols are not exported properly. This is related to the 
https://github.com/openjdk/jdk/pull/20837#discussion_r1744611776 discussion 
comment thread.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/20837#issuecomment-2436496612

Reply via email to