> I've started with a autoconf file for the multiprocessing backport
> package. The tests should produce the same set of definitions but I'm
> not able to test it on different platforms expect Linux.
> http://python-multiprocessing.googlecode.com/svn/trunk/configure.ac
If you want to see how it fa
Jesse Noller wrote:
> Christian - I would appreciate it if we could coordinate/track this on
> the tracker too - I had no idea you were doing this in the back port,
> and I don't think we want the two code bases to diverge that much.
You could not have known about the idea because I started the ex
On Mon, Mar 23, 2009 at 10:31 AM, Christian Heimes wrote:
> Martin v. Löwis wrote:
>> I think multiprocessing is misguided in hard-coding these settings
>> into setup.py. As we can see, the necessary features are available
>> on some versions of Solaris, but not on others. It would be better
>> if
Martin v. Löwis wrote:
> I think multiprocessing is misguided in hard-coding these settings
> into setup.py. As we can see, the necessary features are available
> on some versions of Solaris, but not on others. It would be better
> if autoconf tests were written, and the entire configuration remove
Martin v. Löwis wrote:
>> Sorry, I mistakenly said "without issue" and then copied the issues
>> below. I meant to say "not without issues." _multiprocessing does *not*
>> build on Solaris 8.
>
> Hmm. They are all warnings - did you omit the actual error message?
>
> The lack of CMSG_LEN seems to
> Sorry, I mistakenly said "without issue" and then copied the issues
> below. I meant to say "not without issues." _multiprocessing does *not*
> build on Solaris 8.
Hmm. They are all warnings - did you omit the actual error message?
The lack of CMSG_LEN seems to suggest that control messages are
Christian Heimes wrote:
> Martin v. Löwis schrieb:
>>> According to the user's experience multiprocessing should not compile
>>> and run correctly unless this patch is applied.
>> Can this please be more qualified? I can confirm Scott's observation:
>> for the trunk, it compiles just fine, using Su
Martin v. Löwis schrieb:
>> According to the user's experience multiprocessing should not compile
>> and run correctly unless this patch is applied.
>
> Can this please be more qualified? I can confirm Scott's observation:
> for the trunk, it compiles just fine, using SunPro CC on Solaris 10,
> on
> According to the user's experience multiprocessing should not compile
> and run correctly unless this patch is applied.
Can this please be more qualified? I can confirm Scott's observation:
for the trunk, it compiles just fine, using SunPro CC on Solaris 10,
on SPARC. Also, test_multiprocessing
On Fri, Mar 20, 2009 at 9:51 PM, wrote:
> Jesse> Known issue:
>
> Jesse> http://bugs.python.org/issue3110
>
> Jesse> I haven't had time to look into it, I was planning on working on
> Jesse> many of the mp bugs during the sprint at pycon.
>
> Jesse, I will be at the sprints for a coup
Jesse> Known issue:
Jesse> http://bugs.python.org/issue3110
Jesse> I haven't had time to look into it, I was planning on working on
Jesse> many of the mp bugs during the sprint at pycon.
Jesse, I will be at the sprints for a couple days and should be able to test
things out on So
Jesse Noller wrote:
> On Fri, Mar 20, 2009 at 8:50 PM, Christian Heimes wrote:
>> Martin v. Löwis schrieb:
Today I was in contact with a Python user who tried to compile
pyprocessing - the ancestor of multiprocessing - on Solaris. It failed
to run because Solaris is missing two feat
On Fri, Mar 20, 2009 at 8:50 PM, Christian Heimes wrote:
> Martin v. Löwis schrieb:
>>> Today I was in contact with a Python user who tried to compile
>>> pyprocessing - the ancestor of multiprocessing - on Solaris. It failed
>>> to run because Solaris is missing two features (HAVE_FD_TRANSFER and
Martin v. Löwis schrieb:
>> Today I was in contact with a Python user who tried to compile
>> pyprocessing - the ancestor of multiprocessing - on Solaris. It failed
>> to run because Solaris is missing two features (HAVE_FD_TRANSFER and
>> HAVE_SEM_TIMEDWAIT). Does anybody have a Solaris box at his
Known issue:
http://bugs.python.org/issue3110
I haven't had time to look into it, I was planning on working on many
of the mp bugs during the sprint at pycon.
On Fri, Mar 20, 2009 at 8:18 PM, Christian Heimes wrote:
> Hello fellow co-developers!
>
> Today I was in contact with a Python user who
> Today I was in contact with a Python user who tried to compile
> pyprocessing - the ancestor of multiprocessing - on Solaris. It failed
> to run because Solaris is missing two features (HAVE_FD_TRANSFER and
> HAVE_SEM_TIMEDWAIT). Does anybody have a Solaris box at his disposal to
> test the setti
Hello fellow co-developers!
Today I was in contact with a Python user who tried to compile
pyprocessing - the ancestor of multiprocessing - on Solaris. It failed
to run because Solaris is missing two features (HAVE_FD_TRANSFER and
HAVE_SEM_TIMEDWAIT). Does anybody have a Solaris box at his disposa
17 matches
Mail list logo
