Re: Python i686 vs x86_64 -- for testing a python library

2012-03-27 Thread Richard Shaw
On Tue, Mar 27, 2012 at 11:09 AM, Martin Langhoff wrote: > On Tue, Mar 27, 2012 at 11:18 AM, Adam Jackson wrote: >> Use a chroot or an i686 vm.  Or possibly just do rpmdev-extract on the i686 >> version and run it directly. > > I've been toying with a chroot via mock, but was awkward for a number

Re: Python i686 vs x86_64 -- for testing a python library

2012-03-27 Thread Martin Langhoff
On Tue, Mar 27, 2012 at 11:18 AM, Adam Jackson wrote: > Welcome to rpm.  ELF files have a wacky concept called "color", which means Color me impressed. That's one thing I didn't know! > Use a chroot or an i686 vm.  Or possibly just do rpmdev-extract on the i686 > version and run it directly. I'

Re: Python i686 vs x86_64 -- for testing a python library

2012-03-27 Thread Adam Jackson
On 3/27/12 10:39 AM, Martin Langhoff wrote: I am diagnosing a bug/odditywith a python library that uses Pyrex and other oddities. In the course of that, I have installed python.i686 on my F16 x86_64 system, and I'm trying to run it and... no dice! According to rpm, python.x86_64 and python.i686

Python i686 vs x86_64 -- for testing a python library

2012-03-27 Thread Martin Langhoff
I am diagnosing a bug/odditywith a python library that uses Pyrex and other oddities. In the course of that, I have installed python.i686 on my F16 x86_64 system, and I'm trying to run it and... no dice! According to rpm, python.x86_64 and python.i686 both own /usr/bin/python and /usr/bin/python2.