On Thu, Feb 9, 2012 at 12:55 PM, Ned Deily wrote:
>> 1) I thought distutils took care of calling the "right" compliler to
>> match what pyotn had been built with. I guess not.
>
> Distutils *does* try to call the right CC compiler (that is, the
> compiler the Python itself was built with), unless
In article
,
Chris Barker wrote:
> On Thu, Feb 9, 2012 at 11:37 AM, Russell E. Owen wrote:
>
> > I suggest you try one of these things:
> > - Use gcc 4.0.1 to build extensions for 32-bit python.org python. That's
> > what I'm still doing. It requires XCode 3.x.
>
> Thanks -- I"ll try that. b
In article ,
"Russell E. Owen" wrote:
> I suggest you try one of these things:
> - Use gcc 4.0.1 to build extensions for 32-bit python.org python. That's
> what I'm still doing. It requires XCode 3.x.
Yes.
> - Use gcc 4.2.1 to build extensions for 64-bit python.org python. Two
> issues:
>
On Thu, Feb 9, 2012 at 11:37 AM, Russell E. Owen wrote:
> I suggest you try one of these things:
> - Use gcc 4.0.1 to build extensions for 32-bit python.org python. That's
> what I'm still doing. It requires XCode 3.x.
Thanks -- I"ll try that. but:
1) I thought distutils took care of calling th
In article
,
Chris Barker wrote:
> darn, forgot to send to the list again -- I hate these defaults!
>
>
>
> -- Forwarded message --
> From: Chris Barker
> Date: Thu, Feb 9, 2012 at 9:58 AM
> Subject: Re: [Pythonmac-SIG] distutils and stdarg.h
> To: Ronald Oussoren
>
>
> O
darn, forgot to send to the list again -- I hate these defaults!
-- Forwarded message --
From: Chris Barker
Date: Thu, Feb 9, 2012 at 9:58 AM
Subject: Re: [Pythonmac-SIG] distutils and stdarg.h
To: Ronald Oussoren
On Wed, Feb 8, 2012 at 11:33 PM, Ronald Oussoren wrote:
>> ag
