On Wed, Jun 08, 2016 at 08:38:48AM +0000, Petr Pisar wrote:
> Because "#include <stdlib.h>" fails without stdlib.h on the system,
> you need to depend on something that provides the stdlib.h. And
> guidelines says the provider is "gcc".
gcc doesn't provide stdlib.h, glibc-headers does. But even for the headers
gcc provides (like <stdarg.h>), it makes sure the headers are either arch
independent or in some other way usable for all multilibs.
>
> >>But it's not possible to install gcc.x86_64 and gcc.i686 at the same
> >>time (they conflicts on /usr/libexec/getconf/default).
Sure, don't do it then.
> >>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?
> >
> "Requires: gcc%{?_isa}" in *-devel packages.
Any package that has this should be fixed not to do that.
gcc is carefully split into non-multilib and multilib subpackages, and that
is not going to change.
>
> > The 'gcc' package doesn't install any multilib headers, so why do you
> > need gcc%{?_isa} ?
> >
> <https://fedoraproject.org/wiki/Packaging:C_and_C%2B%2B#BuildRequires_and_Requires>.
Those guidelines don't tell you to require gcc%{?_isa}, only gcc (or
gcc-c++).
Jakub
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
