Bug 700977 - Can't build gcc on i686 - No Package found for /lib64/libc.so.6
Summary: Can't build gcc on i686 - No Package found for /lib64/libc.so.6
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: 14
Hardware: i686
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-30 06:21 UTC by Piscium
Modified: 2011-04-30 08:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-30 06:46:51 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Piscium 2011-04-30 06:21:51 UTC 
Description of problem:

I can't build gcc on i686. After downloading the gcc source package, if I run yum-builddep I get "Error: No Package found for /lib64/libc.so.6".

This was also an issue in F13.

There is an easy workaround. I comment out this line in the spec file:
#%global multilib_64_archs sparc64 ppc64 s390x x86_64

After that I rebuild the source package and can run yum-builddep successfully.

So this is a minor issue, but it would be nice if it could be fixed as there are still people using Fedora on 32 bits computers.


Version-Release number of selected component (if applicable):
gcc-4.5.1-4.fc14.src.rpm


How reproducible:
Always
Comment 1 Jakub Jelinek 2011-04-30 06:46:51 UTC 
The buildrequires in gcc.spec are arch specific, if yum-builddep uses Requires: stored in the src.rpm instead of parsing the spec file, the result will depend on which architecture the src.rpm has been built on.  You don't need to uncomment anything, just rebuild the src.rpm or use mock which can handle the conditional dependencies.
Comment 2 Piscium 2011-04-30 08:13:52 UTC 
How do I rebuild the src.rpm? Normally I would do:
rpm -Uvh package.rpm 
cd ../SPECS
rpmbuild -bs package.spec

Is there a better way to rebuild it?
Note You need to log in before you can comment on or make changes to this bug.