Bug 979314 - gcc: architecture-dependent build requirements
gcc: architecture-dependent build requirements
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: gcc (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jakub Jelinek
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-28 04:12 EDT by Florian Weimer
Modified: 2013-07-04 12:36 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-07-04 12:36:14 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Florian Weimer 2013-06-28 04:12:29 EDT
This package computes its build requirements at the time the SRPM is built, depending on the SRPM build architecture:

%global multilib_64_archs sparc64 ppc64 s390x x86_64
[…]
%ifarch %{multilib_64_archs} sparcv9 ppc
# Ensure glibc{,-devel} is installed for both multilib arches
BuildRequires: /lib/libc.so.6 /usr/lib/libc.so /lib64/libc.so.6 /usr/lib64/libc.so
%endif

This is against the spirit, if not the letter, of the Fedora Packaging Guidelines: <http://fedoraproject.org/wiki/Packaging:Guidelines#BuildRequires_and_.25.7B_isa.7D>
Comment 1 Jakub Jelinek 2013-06-28 05:02:25 EDT
But the src.rpm really has those architecture dependent dependencies, it won't build properly without those.  So, unless you have a suggestion what to do instead, I'll close this as WONTFIX.
Comment 2 Florian Weimer 2013-06-28 10:26:31 EDT
(In reply to Jakub Jelinek from comment #1)
> But the src.rpm really has those architecture dependent dependencies, it
> won't build properly without those.  So, unless you have a suggestion what
> to do instead, I'll close this as WONTFIX.

Yes, I can see that.  I now wonder if the FPC decision to include this particular language (*MUST NOT*) in the guidelines was wrong.  It's still a good idea to avoid arch-specific build requirements n general, but toolchain packages are an obvious exception.

Note You need to log in before you can comment on or make changes to this bug.