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 vinay.sajip
Recipients amaury.forgeotdarc, giampaolo.rodola, mluis, neologix, ogait87, orsenthil, pitrou, python-dev, rosslagerwall, slanden, vinay.sajip, vstinner
Date 2011-10-07.16:31:25
SpamBayes Score 7.9308654e-07
Marked as misclassified No
Message-id <1318005086.05.0.139978156254.issue10141@psf.upfronthosting.co.za>
In-reply-to
Content
PF_CAN is defined by

#define PF_CAN		AF_CAN

in linux/socket.h :-(

Making the change in configure.in didn't lead to any change: no error when I ran configure (which is ./configure --with-py-debug in my case), and when I build, the same error (AF_CAN undefined) occurs. Just to eliminate any extraneous variables and be absolutely sure, the program

#include <sys/socket.h>
#include <stdio.h>

int main(int argc, char ** argv)
{
    printf("AF_CAN is %d\n", AF_CAN);
}

also fails with the same error.
History
Date User Action Args
2011-10-07 16:31:26vinay.sajipsetrecipients: + vinay.sajip, amaury.forgeotdarc, orsenthil, pitrou, vstinner, giampaolo.rodola, neologix, slanden, rosslagerwall, python-dev, ogait87, mluis
2011-10-07 16:31:26vinay.sajipsetmessageid: <1318005086.05.0.139978156254.issue10141@psf.upfronthosting.co.za>
2011-10-07 16:31:25vinay.sajiplinkissue10141 messages
2011-10-07 16:31:25vinay.sajipcreate