Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
ocaml currently does not build with glibc 2.34 because its signal stack allocation code assumes a constant stack size requirement. In Fedora, this apparently was addressed in this commit:
commit b8653f50ff7bc66cac91dcf67a45317c557f8a27
Author: Richard W.M. Jones <rjones>
Date: Sun Feb 28 20:53:29 2021 +0000
OCaml 4.12.0 release (RHBZ#1893381).
Workaround for glibc non-constant SIGSTKSZ
(https://github.com/ocaml/ocaml/issues/10250)
This issue will start impacting ocaml in Red Hat Enterprise Linux 9 once we switch to glibc 2.34.
You can test a fix before glibc 2.34 is merged using this command:
koji -p stream build --scratch c9s-build-side-102-stack-gate git+https://gitlab.com/redhat/centos-stream/rpms/ocaml#origin/c9s
Comment 1Richard W.M. Jones
2021-06-23 10:46:29 UTC
This one cannot be easily tested.
However the package will fail to build with glibc 2.34, so probably
the best testing method is to check if it has been built against
glibc 2.34, and if it didn't fail to build then it's good.
Comment 2Richard W.M. Jones
2021-06-23 11:21:21 UTC
I'm marking this bug as fixed and adding it to the erratum, but
note that the actual build:
https://kojihub.stream.rdu2.redhat.com/koji/taskinfo?taskID=330196
was NOT done against glibc 2.34 (but against 2.33). I assume
some kind of mass rebuild is planned for that.
Comment 3Richard W.M. Jones
2021-06-23 11:24:04 UTC
(In reply to Richard W.M. Jones from comment #4)
> As a result of this we have to rebuild all the other ocaml-* packages :-(
Sorry about that. Note that it would have been technically possible to rebuild the packages with a reference to this bug.
ocaml currently does not build with glibc 2.34 because its signal stack allocation code assumes a constant stack size requirement. In Fedora, this apparently was addressed in this commit: commit b8653f50ff7bc66cac91dcf67a45317c557f8a27 Author: Richard W.M. Jones <rjones> Date: Sun Feb 28 20:53:29 2021 +0000 OCaml 4.12.0 release (RHBZ#1893381). Workaround for glibc non-constant SIGSTKSZ (https://github.com/ocaml/ocaml/issues/10250) This issue will start impacting ocaml in Red Hat Enterprise Linux 9 once we switch to glibc 2.34. You can test a fix before glibc 2.34 is merged using this command: koji -p stream build --scratch c9s-build-side-102-stack-gate git+https://gitlab.com/redhat/centos-stream/rpms/ocaml#origin/c9s