Scott David Daniels wrote:
I encourage anyone who gets further into solving the "How do I use
MinGW to build Python2.4 (and later) standard-distribution compatible
modules (.pyd s)?" question to share any clues they have. The MS
free compiler is useful to many, but not all of us.
I think the simpl
[EMAIL PROTECTED] wrote:
And so I suspect this approach (compiling sources yourself) can shield
people from this ugly mess, if they can build Python 2.4 and the
extensions and have them (core and extension) use one and the same
run-time library. But indeed this might be an issue for those who [1]
u
Martin v. Löwis wrote:
> Indeed, it *will* work most of the time, as you rarely pass resources
> across CRTs in a typical Python extension. However, it is very hard
> to tell from the source code of the extension if such resource
passing
> could ever happen (e.g. what about setlocale(), atexit(), m
[EMAIL PROTECTED] wrote:
Believe it or not I do not get a crash here.
I can believe this. strdup does malloc, i.e. gets some
memory from the heap, and free puts it back into the heap.
Since this is a different CRT, it puts it back into
a different heap. This is a leak, but it should not cause
a cra
From: "" <[EMAIL PROTECTED]>
Newsgroups: comp.lang.python
Subject: Re: Problem with msvcrt60 vs. msvcr71 vs. strdup/free
Date: Wed, 22 Dec 2004 11:07:02 -0800
Gerhard Haering wrote:
> Hello,
>
> I used to build Python extension modules with mingw. Now, Python has
> swi
From: "Gerhard Haering"
>Is there any way I can force mingw to not link in msvcr for things
>like strdup?
mdkdir /mingw/lib/msvcr71
cp -f libmsvcr71.a /mingw/lib/msvcr71/libmsvcrt.a
gcc ${OBJECTS} -L /mingw/lib/msvcr71
Or you could hand edit gcc's specs file, replacing -lmsvcrt with -lwhatever..
Hello,
I used to build Python extension modules with mingw. Now, Python has
switched to the MSVCR71 runtime with version 2.4, and I thought mingw
has support for this. But I get problems with symbols being referenced
from the wrong DLLs.
You can see the problem by compiling this:
###
Gerhard Haering <[EMAIL PROTECTED]> writes:
> Hello,
>
> I used to build Python extension modules with mingw. Now, Python has
> switched to the MSVCR71 runtime with version 2.4, and I thought mingw
> has support for this. But I get problems with symbols being referenced
> from the wrong DLLs.
>
>
Of not so much interest to most Pythoneers, but ...
I cross-posted this to python-list to make people aware that thare are
*real* problems with mingw + Python 2.4, not only theoretical ones.
-- Gerhard
signature.asc
Description: Digital signature
--
http://mail.python.org/mailman/listinfo/pyth
