Hello,
On Thu, 2025-12-11 at 17:45 +0100, Rene Engelhard wrote:
OK, was wondering whether OpenJDK choked on it. Then the fix would be to either
a)
$ cat remove-JITC_PROCESSOR_TYPE-setting.diff
[...]
thus triggering the cp or
I think it should be safe to drop the complete handling for JITC_PROCESSOR_TYPE_EXPORT.
There is no JDK by IBM for 32-bit anymore, so all of this has become cruft.
[...]
b) is cleaner and minimal-invasive.
Yes, but we can just drop all of this. I don't think that upstream is interested in keeping this.