Re: Hacks for multilib unclean C headers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 08/06/16 07:37 +0000, Petr Pisar wrote:
Guidelines require devel packages to be architecture specific (no
BuildArch: noarch). Guidelines require having dependencies between
architecture specific packages restricted to the architecture
(Requires: foo-devel%{?_isa}). C guildelines require depending on "gcc"
for standard C library header files.

Files in devel packages usually include standard C library header
files, thus one needs to "Require: gcc%{?_isa}" from the devel packages.

Why?

But it's not possible to install gcc.x86_64 and gcc.i686 at the same
time (they conflicts on /usr/libexec/getconf/default).

So the final question: When gcc package will be multilib-safe? Without
multlib-safe gcc package, all the aim in all the other packages is
useless because all the dependencies lead to gcc.

Which dependencies?

The 'gcc' package doesn't install any multilib headers, so why do you
need gcc%{?_isa} ?

I can see how you might need libstdc++-devel%{?_isa} or other
components of GCC, but those *are* multilibbed, so you can have both
libstdc++-devel.i686 and libstdc++-devel.x86_64 installed at the same
time.

--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux