On 01/12/2018 06:03 PM, Erik Joelsson wrote:
Which I would expect to cover your case, unless there is a mismatch between
s390 and s390x here. Is your OPENJDK_TARGET_CPU set to s390 or s390x in this
case? If this discrepancy between arch names cannot be resolved, then a special
case like the
Hello Adam,
Configure already looks in:
$SYSROOT/usr/lib/$OPENJDK_TARGET_CPU-linux-gnu
Which I would expect to cover your case, unless there is a mismatch
between s390 and s390x here. Is your OPENJDK_TARGET_CPU set to s390 or
s390x in this case? If this discrepancy between arch names cannot
Looks good to me.
/Erik
On 2018-01-11 21:24, David Buck wrote:
Hi!
May I please get a review of my backport of this small change:
bug report:
https://bugs.openjdk.java.net/browse/JDK-8187045
JDK 10 review thread:
http://mail.openjdk.java.net/pipermail/build-dev/2017-September/019723.html
On 01/12/2018 03:29 PM, Adam Farley8 wrote:
>> On zLinux, freetype's .so file is typically installed in
>> /usr/lib/s390x-linux-gnu, however the generated configure script
doesn't
>> look for it there.
>
>Odd. Normally I would expect it to look in the locations that are
>set through
On 01/12/2018 03:29 PM, Adam Farley8 wrote:
On zLinux, freetype's .so file is typically installed in
/usr/lib/s390x-linux-gnu, however the generated configure script doesn't
look for it there.
Odd. Normally I would expect it to look in the locations that are
set through /etc/ld.so.conf{,.d}
Hi All,
On zLinux, freetype's .so file is typically installed in
/usr/lib/s390x-linux-gnu, however the generated configure script doesn't
look for it there.
This causes configure to fail. I know you can avoid that with options, but
I think a fix would be better.
If we add this code to
