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.
Created attachment 1804431[details]
build.log
Rebuilding curl-7.76.1-6.el9 shows this error in the build log:
valgrind ERROR --2171514-- WARNING: unhandled amd64-linux syscall: 435
--2171514-- You may be able to write your own handler.
--2171514-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--2171514-- Nevertheless we consider this a bug. Please report
--2171514-- it at http://valgrind.org/support/bug_reports.html.
And there are test failures. This is likely caused by valgrind bug 1984076. I will re-check once the fixed valgrind lands in the buildroot.
(In reply to Kamil Dudka from comment #1)
> Thank you for reporting it! It appears fixed now:
>
> https://kojihub.stream.rdu2.redhat.com/koji/buildinfo?buildID=10045
Just to be clear, this build was against a glibc without clone3 and an unfixed valgrind. I forgot to mention that the glibc with clone3 is currently only in a side tag (until valgrind and likely firefox can be fixed).