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 one you propose is needed.
From Adam's last mail it seems there is something wrong with his build environment:
From the configure output, it appears to look for it in x86_64-linux-gnu so I don't know what to tell you.
So, we need to figure out first the configure is looking in x86_64-linux-gnu on the s390x environment. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
