Windows build failure when building JLI
David Holmes
david.holmes at oracle.com
Mon Sep 3 11:12:28 UTC 2012
Hi Artem,
That sounds like some recent command-line parsing changes for wildcards
didn't get applied to the new build files.
cc'ing Kumar as the author of those changes.
David
On 3/09/2012 8:37 PM, 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
More information about the build-dev
mailing list