On Mon, May 23, 2011 at 2:08 PM, Chris Angelico wrote:
> Currently I'm puzzling over an inordinate number of symbol-not-found
> errors, even though it does seem to be finding the header files. It's
> weird.
And I think I've just figured out why. PyString_* functions are no
longer supported -
On Mon, May 23, 2011 at 2:01 PM, Ned Deily wrote:
> It's a new feature in Python 3.2 to allow multiple versions of shared C
> object files that differ in configure options (i.e. ones that affect the
> Python C ABI) to co-exist in one Python installation. "m" means that
> they were built with pyma
In article ,
Chris Angelico wrote:
> Question: Why "3.2m"? What does that m mean? It seems to have come up
> a couple of times in the build process.
It's a new feature in Python 3.2 to allow multiple versions of shared C
object files that differ in configure options (i.e. ones that affect the
Hi! Just a quickie, I hope, where someone will probably be able to
answer off the top of his head.
I downloaded the 3.2 sources with the intention of building that
instead of using Ubuntu's default Python 2.6.6. Ran ./configure, make,
sudo make install, and then fiddled with a few things like make
