On Tue, May 16, 2006 at 10:48:39AM -0400, seth vidal wrote:
On Tue, 2006-05-16 at 11:33 +0200, Florian La Roche wrote:
> On Tue, May 16, 2006 at 11:25:43AM +0200, Andreas Thienemann wrote:
> > Hello,
> >
> > I noticed some problems with mock, when building tools such as valgrind,
> > syslinux etc. on x86_64.
> >
> > The default mock config says to exclude i386 and similar packages.
> >
> > However, these programs depend on stubs-32.h from the i386 glibc-devel
> > package.
> > The x86_64 glibc-devel only brings stubs-64.h, which makes the compilation
> > of these tools stop, because stubs-32.h could not be found.
> >
> > What would be the correct way of fixing this?
>
> You should still keep the 32bit glibc rpm packages.
>
> I've had this running at some point with the following yum repo:
> [devel-x86_64]
> name=Fedora Core Development for x86_64
> baseurl=file:/mnt/raid/fedora/development/x86_64
> exclude=*-debuginfo-* [!g]*.i686 [!g]*.i386 g[!l]*.i386 glib.i386 glib2.i386
>
>
> Not sure the above still works or if there are nicer ways now todo the
> same within mock via other mechanisms. It should be something like
> "exclude all *.i686/*.i386 packages, but still keep glibc*.i686
installed".
>
>
So you're saying that in order to build 64bit packages we REQUIRE
glibc*.i686?
Are you serious? So there's no way to build x86_64 w/o i386 first being
built?
Hello Seth,
No, just that glibc is an exception to the otherwise "only install 64bit
rpm packages" rule for a buildroot.
regards,
Florian La Roche