Building openjdk with glibc >= 2.24
Kim Barrett
kim.barrett at oracle.com
Mon Apr 9 06:16:58 UTC 2018
> On Apr 9, 2018, at 2:11 AM, David Holmes <david.holmes at oracle.com> wrote:
>
> Hi Jan,
>
> Already being discussed on the build-dev list. See:
>
> http://mail.openjdk.java.net/pipermail/build-dev/2018-March/021154.html
>
> and continuing:
>
> http://mail.openjdk.java.net/pipermail/build-dev/2018-April/021530.html
Also here:
http://mail.openjdk.java.net/pipermail/hotspot-dev/2018-March/030773.html
where a fix was proposed (use ::readdir()), but not followed up on. And there’s
no bug report in the bug system yet.
>
> David
>
> On 9/04/2018 7:53 AM, Jan Schlößin wrote:
>> Hello List,
>> I tried to compile openjdk (from hg.openjdk.java.net/jdk/jdk) on my
>> linux box (current changeset 8bdf2b5f472d). I succeeded after using
>> --disable-warnings-as-errors with the configure script. The reason is
>> that some files are referencing readdir_r and readdir64_r despite been
>> deprecated with glibc 2.24 in mid 2016!!!
>> Deprecated functions are not going away necessarily. But since you are
>> treating deprecation warnings as errors by default it might be a good
>> idea to use readdir and readdir64 in favor to the deprecated ones or
>> don't treat deprecation warnings as errors in the first place.
>> It would be nice to have openjdk build on a decent linux system like it
>> is described in doc/build.html.
>> I think the functions have been deprecated because the plain readdir
>> version (without *_r) became reentrant, too. But I'm not sure about it.
>> -Jan
More information about the jdk-dev
mailing list