Building Python: static library "3.2m"

[Chris Angelico]

On Mon, May 23, 2011 at 2:01 PM, Ned Deily <nad at acm.org> 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 pymalloc.  Other flags are "d" for debug, and "u"
> for wide-unicode.

Ahh, thank you! I was planning to just statically link to my
executable to reduce deployment effort, but either way works.
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.

Chris Angelico