[EMAIL PROTECTED] schrieb:
> Martin> The problem you have is specific to Solaris, and specific to
> Martin> using GCC on Solaris.
>
> So can we fix this in pyport.h or with suitable Configure script
> machinations? Even though the current patch we're using is trivial I'd
> really like to
Martin> The problem you have is specific to Solaris, and specific to
Martin> using GCC on Solaris.
So can we fix this in pyport.h or with suitable Configure script
machinations? Even though the current patch we're using is trivial I'd
really like to avoid patching the Python distributio
[EMAIL PROTECTED] schrieb:
> One of our C++ gurus (that's definitely not me!) patched the Python source
> to include at the top of Python.h. That seems to have solved our
> problems, but seems to be a symptomatic fix.
Indeed. The right fix is likely different, and relates to the question
what AP
On Sep 13, 2006, at 18:46, [EMAIL PROTECTED] wrote:
>
> Building Python with C and then linking in extensions written in or
> wrapped
> with C++ can present problems, at least in some situations. I
> don't know if
> it's kosher to build that way, but folks do. We're bumping into such
> prob
