Python i686 vs x86_64 -- for testing a python library
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.7 . Those binaries are 64 bits. Googling around, I cannot find any clue on how to run the 32 bit binary. Had optimistically assumed that I'd find python.i686 stashed somewhere when I looked at rpm -ql python.686 ... cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Python i686 vs x86_64 -- for testing a python library
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 both own /usr/bin/python and /usr/bin/python2.7 . Those binaries are 64 bits. Googling around, I cannot find any clue on how to run the 32 bit binary. Had optimistically assumed that I'd find python.i686 stashed somewhere when I looked at rpm -ql python.686 ... Welcome to rpm. ELF files have a wacky concept called color, which means you can have both .i686 and .x86_64 versions of the same package installed with no conflict and the x86_64 version wins on disk. Use a chroot or an i686 vm. Or possibly just do rpmdev-extract on the i686 version and run it directly. - ajax -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Python i686 vs x86_64 -- for testing a python library
On Tue, Mar 27, 2012 at 11:18 AM, Adam Jackson a...@redhat.com 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've been toying with a chroot via mock, but was awkward for a number of reasons. I've used rpmdev-extract and installed just the binary as /usr/bin/python2.6-i686 Saved my day -- thanks! m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Python i686 vs x86_64 -- for testing a python library
On Tue, Mar 27, 2012 at 11:09 AM, Martin Langhoff martin.langh...@gmail.com wrote: On Tue, Mar 27, 2012 at 11:18 AM, Adam Jackson a...@redhat.com 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 of reasons. I've used rpmdev-extract and installed just the binary as /usr/bin/python2.6-i686 Yeah, it's a little awkward since it's not really made for that purpose but it does work well, a la: mock --init mock --install packages mock --shell Of course you need to set a default release and arch to use or just use the -r fedora-release-arch option. I frequently use this method to run rpmlint on installed packages without having to pollute my main system. Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
