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.

Bug 1338917

Summary: /usr/include/gnu/stubs.h:10:27: fatal error: gnu/stubs-64.h: No such file or directory
Product: Red Hat Enterprise Linux 7 Reporter: Jan Stodola <jstodola>
Component: php-pecl-memcacheAssignee: Remi Collet <rcollet>
Status: CLOSED DUPLICATE QA Contact: RHEL Stacks Subsystem QE <rhel-stacks-subsystem-qe>
Severity: high Docs Contact:
Priority: high    
Version: 7.2CC: djez, jorton, lmiksik
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-17 16:01:34 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: 1256306, 1473612    

Description Jan Stodola 2016-05-23 16:06:10 UTC
Description of problem:
When running kickstart installation of RHEL-7.2 and installing all package set, including multilib packages, there is an error reported while installing php-pecl-memcache:

...
15:32:57,970 INFO packaging: php-pecl-memcache-3.0.8-4.el7.x86_64 (2694/4617)
15:32:57,970 INFO packaging: In file included from /usr/include/features.h:399:0,
15:32:57,970 INFO packaging:                  from /tmp/glibctestEMyoVg:1:
15:32:57,970 INFO packaging: /usr/include/gnu/stubs.h:10:27: fatal error: gnu/stubs-64.h: No such file or directory
15:32:57,970 INFO packaging:  # include <gnu/stubs-64.h>
15:32:57,971 INFO packaging:                            ^
15:32:57,971 INFO packaging: compilation terminated.
15:32:57,971 INFO packaging: php-odbc-5.4.16-36.el7_1.x86_64 (2695/4617)
...


gnu/stubs-64.h comes from glibc-devel, which is installed later in the transaction:

...
15:32:57,975 INFO packaging: glibc-devel-2.17-105.el7.x86_64 (2748/4617)
...


Version-Release number of selected component (if applicable):
RHEL-7.2 GA
php-pecl-memcache-3.0.8-4.el7
glibc-devel-2.17-105.el7

How reproducible:
always on RHEL-7.2 (x86_64/Server)

Steps to Reproduce:
1. run kickstart installation with the following %packages section:

%packages --multilib
*
-@conflicts-Server
%end

2. check /var/log/anaconda/packaging.log when the installation is done

Actual results:
errors when installing php-pecl-memcache

Expected results:
no errors

Comment 7 Joe Orton 2020-01-17 16:01:34 UTC
Full diagnosis/discussion in bug 1720375 hence moving there.

*** This bug has been marked as a duplicate of bug 1720375 ***