Message214343
| Author |
vinay.sajip |
| Recipients |
amaury.forgeotdarc, giampaolo.rodola, mluis, neologix, ogait87, orsenthil, pitrou, python-dev, rosslagerwall, slanden, vinay.sajip, vstinner |
| Date |
2014年03月21日.11:02:19 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1395399740.15.0.0169249200613.issue10141@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> What error were you getting?
That AF_CAN was undefined (even though HAVE_LINUX_CAN_H is). This is on Ubuntu Jaunty, which I use for my Python core development.
Note the change you made in d4ce850b06b7 to fix this problem when it occurred before - it's the same approach as my recent change that we're talking about. It seems that in 3.4, some more instances of AF_CAN usage were added, but wrapped in #ifdef HAVE_LINUX_CAN_H, which led to the new compilation failures.
I'll make the changes to take CAN_RAW into account. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2014年03月21日 11:02:20 | vinay.sajip | set | recipients:
+ vinay.sajip, amaury.forgeotdarc, orsenthil, pitrou, vstinner, giampaolo.rodola, neologix, slanden, rosslagerwall, python-dev, ogait87, mluis |
| 2014年03月21日 11:02:20 | vinay.sajip | set | messageid: <1395399740.15.0.0169249200613.issue10141@psf.upfronthosting.co.za> |
| 2014年03月21日 11:02:20 | vinay.sajip | link | issue10141 messages |
| 2014年03月21日 11:02:19 | vinay.sajip | create |
|