Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1838674

Summary: proxysql-2.0.9-4.fc33 FTBFS: src/elfcore.c:52:10: fatal error: sys/sysctl.h: No such file or directory
Product: [Fedora] Fedora Reporter: Petr Pisar <ppisar>
Component: proxysqlAssignee: Michal Schorm <mschorm>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: high    
Version: rawhideCC: acaringi, fjanus, hhorak, igor.raits, ljavorsk, mschorm
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://koschei.fedoraproject.org/package/proxysql?collection=f33
Whiteboard:
Fixed In Version: proxysql-2.0.13-1.fc33 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-04 10:15:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1803234    

Description Petr Pisar 2020-05-21 14:43:43 UTC
proxysql-2.0.9-4.fc33 fails to build in Fedora 33:

libtool: compile:  cc -DHAVE_CONFIG_H -I. -I./src -I./src -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -fno-strict-aliasing -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -MT src/elfcore.lo -MD -MP -MF src/.deps/elfcore.Tpo -c src/elfcore.c  -fPIC -DPIC -o src/.libs/elfcore.o
src/elfcore.c:52:10: fatal error: sys/sysctl.h: No such file or directory
   52 | #include <sys/sysctl.h>
      |          ^~~~~~~~~~~~~~
compilation terminated.

This is triggered by a glibc change:

* Wed Apr 15 2020 Patsy Griffin <patsy> - 2.31.9000-9
- Auto-sync with upstream branch master,
  commit 076f09afbac1aa57756faa7a8feadb7936a724e4.
- Linux: Remove <sys/sysctl.h> and the sysctl function
- posix: Add wait4 test case
- linux: wait4: Fix incorrect return value comparison
- hurd: add mach_print function
- x32: Properly pass long to syscall [BZ #25810]
- Add GRND_INSECURE from Linux 5.6 to sys/random.h
- Update kernel version to 5.6 in tst-mman-consts.py.

Comment 1 Lukas Javorsky 2020-06-23 10:42:02 UTC
I've looked into this one, and found the problem.

Few bundled packages have this failing include inside of their c files:
jemalloc/jemalloc-5.2.0/src/pages.c:12:#include <sys/sysctl.h>
google-coredumper/google-coredumper/src/elfcore.c:52:#include <sys/sysctl.h>

I've tried to update proxysql package to newer version, which may fix this but it failed on the Filip's big patch (proxysql_debundle.patch)

It's kind of difficult for me to understand what exactly is going on there so I'll wait for Filip, because he created it and he will understand it much better than me.

IMHO we should try to just update proxysql to newer version because I think upstream had to fix this already.

Comment 2 Fedora Update System 2020-08-04 09:25:33 UTC
FEDORA-2020-2c1052c64b has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-2c1052c64b

Comment 3 Fedora Update System 2020-08-04 10:15:44 UTC
FEDORA-2020-2c1052c64b has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.