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

Re: Mock x86_64/i386 build issues



On Mon, 2007-10-08 at 10:41 -0600, Orion Poplawski wrote:
> seth vidal wrote:
> > On Mon, 2007-10-08 at 09:36 -0600, Orion Poplawski wrote:
> >> I'm having trouble building some i386 packages (rpm, anaconda) on my 
> >> x86_64 machine with mock.  It seems that the build process picks up that 
> >> the processor in x86_64.  How does koji or anyone else handle this?
> >>
> > 
> > cat /etc/rpm/platform
> > 
> > if it is there remove it.
> 
> Didn't help.  In the anaconda case:
> 
> RPM build errors:
>      File not found by glob: 
> /var/tmp/anaconda-11.3.0.36-1.cora.1-root-mockbuild/usr/lib/python?.?/site-packages/pyisomd5sum.so
>      Installed (but unpackaged) file(s) found:
>     /usr/lib64/python2.5/site-packages/pyisomd5sum.so
> 
> 
> Installed with:
> 
>          install -m 755 pyisomd5sum.so 
> $(DESTDIR)/usr/$(LIBDIR)/$(PYTHON)/site-packages
> 
> LIBDIR is set with:
> 
> FULLARCH := $(shell uname -m)
> 
> ifneq (,$(filter ppc64 x86_64 s390x,$(FULLARCH)))
> LIBDIR = lib64
> else
> LIBDIR = lib
> endif
> 
> 
> $ mock --arch=i386 -r fedora-devel-i386 shell
> init
> mock-chroot> uname -m
> x86_64
> 
> Looks like I need setarch?
> 
> $ setarch i386 mock --arch=i386 -r fedora-devel-i386 shell
> init
> mock-chroot> uname -m
> i686
> 
> Seems like --arch=i386 should take care of this.
> 

you're not even running 'setarch'? Oh - you have to do that - but no,
--arch= won't run setarch for you b/c

1. it doesn't need to know what your running arch is
2. would it then make sense for it to run qemu if you want to build ppc.

so the order of ops:

1. remove /etc/rpm/platform
2. run inside setarch

-sv



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