On Wed, Jan 20, 2016 at 5:59 PM, Michael Schwendt <mschwendt(a)gmail.com> wrote:
On Wed, 20 Jan 2016 21:59:01 +0100, Jan Kratochvil wrote:
> On Wed, 20 Jan 2016 16:50:03 +0100, Richard W.M. Jones wrote:
> > However on the same host if you do:
> >
> > dnf install gtk3-devel.i686
> >
> > then there's a lot missing before you can compile a 32 bit Gtk3
> > application[2].
>
> There were always missing many %{?_isa} in BuildRequires, I was filing many of
> them, got some fixed. But now it is even forbidden to use them:
>
https://fedoraproject.org/wiki/Packaging:Guidelines#BuildRequires_and_.25...
>
This is about explicit and automatic Requires, _not_ BuildRequires.
--
devel mailing list
devel(a)lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Wouldn't there also be the problem of headers getting clobbered when
you do this?
We don't store libraries and headers in such a way that the different
arches can coexist without clobbering. That would be possible if we
have something like this:
/usr/lib/<gcc-platform-id>
/usr/include/<gcc-platform-id>
For example, a 32-bit x86 platform would probably use
"i686-redhat-linux-gnu", whereas a 64-bit x86 platform would use
"x86_64-redhat-linux-gnu".
Without that, it would be tough to guarantee that installing the
32-bit version of a devel package would produce a consistent and sane
build compared to an actual 32-bit chroot.
--
真実はいつも一つ!/ Always, there's only one truth!