Hello Artem,
Unfortunately the new build slowly gets outdated in the jdk8
repositories other than build-infra, where it is being developed. Please
also note that the new build is still only a preview, and we are not yet
guaranteeing correct results from it.
You are correct with the patch. I've done that correction in build-infra
already. We have been meaning to push another update to the new build
from build-infra to jdk8 for a while now. We should probably try to get
that done as soon as possible since people are suffering from this.
If this change is to be applied on its own, it also needs to update the
mapfile:
diff -r 156ab3c38556 makefiles/mapfiles/libjli/mapfile-vers
--- a/makefiles/mapfiles/libjli/mapfile-vers
+++ b/makefiles/mapfiles/libjli/mapfile-vers
@@ -34,6 +34,9 @@
JLI_ReportErrorMessageSys;
JLI_ReportMessage;
JLI_ReportExceptionDescription;
+ JLI_GetStdArgs;
+ JLI_GetStdArgc;
local:
*;
};
/Erik
On 2012-09-03 12:37, Artem Ananiev wrote:
Hi, build-dev,
(please, keep me in CC as I'm not subscribed to this mailing list)
I'm (again) trying to build JDK8 on my Windows box using new build
infrastructure, based on autoconf. The build fails somewhere in JLI
section. I can't provide the error log right now, as I've already
found the workaround:
1. Add cmdtoargs.c to the list of compiled files
Without it the linker complains about unresolved JLI_GetStdArgs and
JLI_GetStdArgc symbols
2. Add several -export: flags, so all the required JLI functions are
exported and can be found by launcher sources (main.c)
Note that the old Makefiles do contain both cmdtoargs.c and exports
listed above. I'm not an expert in building JDK, so it's quite
possible I'm just doing something wrong.
Anyway, here is the webrev:
http://cr.openjdk.java.net/~art/jdk8/build-jli-cmdtoargs/
Please, let me know if this is a bug or a feature and if I need to
file a new change request or not.
Thanks,
Artem
