I've found that:
- recompiling openjade on Debian nowadays makes it exhibit the same behavior
- recompiling openjade in Debian&Ubuntu with gcc-9 also fails the same way

I'd love to find the root cause, but my hope of identifying either a
compiler-default-option or compiler-version that made it break failed.
It stays as it was before, you better not recompile openjade otherwise
you'll need -O0 or find the yet unknown root cause.

IMHO for mostly a doc conversion tool (that also seems mostly dead
upstream) speed isn't super-important and while not perfect -O0 should
be ok'ish for the time being.


For now the mitigation worked, pgpool2 for example now built fine:
  https://launchpad.net/ubuntu/+source/pgpool2/4.1.4-2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869734

Title:
  openjade segfaults on arm (due to gcc optimization)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjade/+bug/1869734/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to