This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author movement
Recipients loewis, movement, srid, zooko
Date 2010-05-31.23:54:41
SpamBayes Score 0.098148294
Marked as misclassified No
Message-id <1275350083.23.0.880687640297.issue8864@psf.upfronthosting.co.za>
In-reply-to
Content
This appears to be one of the few cases where there's incompatibilities between different versions of the standards. Old BSD sockets use msg_accrights*, whereas the more modern way is msg_control*
pointing to a struct cmsghdr.

In terms of user/kernel interface, this difference is encoded as a MSG_XPG4_2 flag via a __xnet_recvmsg() re-define depending upon #ifdef _XPG4_2.

The result being that it's impossible to use C99 and a modern struct msghdr together. This is less than ideal and I'm following it up internally.

In terms of getting Python building again, it should be sufficient to define _XPG4_2 for the multiprocessing module compile only.
History
Date User Action Args
2010-05-31 23:54:43movementsetrecipients: + movement, loewis, zooko, srid
2010-05-31 23:54:43movementsetmessageid: <1275350083.23.0.880687640297.issue8864@psf.upfronthosting.co.za>
2010-05-31 23:54:41movementlinkissue8864 messages
2010-05-31 23:54:41movementcreate