Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #6036 > unrolled thread
| Started by | Chris Angelico <rosuav@gmail.com> |
|---|---|
| First post | 2011-05-23 14:08 +1000 |
| Last post | 2011-05-23 14:08 +1000 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Building Python: static library "3.2m" Chris Angelico <rosuav@gmail.com> - 2011-05-23 14:08 +1000
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2011-05-23 14:08 +1000 |
| Subject | Re: Building Python: static library "3.2m" |
| Message-ID | <mailman.1949.1306123737.9059.python-list@python.org> |
On Mon, May 23, 2011 at 2:01 PM, Ned Deily <nad@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
Back to top | Article view | comp.lang.python
csiph-web