[issue26443] cross building extensions picks up host headers

2016-03-09 Thread Berker Peksag
Changes by Berker Peksag : -- stage: -> resolved superseder: -> setup.py: do not add invalid header locations ___ Python tracker

[issue26443] cross building extensions picks up host headers

2016-03-09 Thread Martin Hundebøll
Martin Hundebøll added the comment: Yes, it is a duplicate of #20211, and I agree with the fix proposed in there. Thanks for pointing it out. -- resolution: -> duplicate status: open -> closed ___ Python tracker

[issue26443] cross building extensions picks up host headers

2016-03-01 Thread Alex Willmer
Alex Willmer added the comment: This looks like a duplicate of #20211, and IMO the patch there is more correct. -- ___ Python tracker ___

[issue26443] cross building extensions picks up host headers

2016-03-01 Thread Alex Willmer
Changes by Alex Willmer : -- nosy: +Alex.Willmer ___ Python tracker ___ ___

[issue26443] cross building extensions picks up host headers

2016-02-27 Thread Ned Deily
Changes by Ned Deily : -- nosy: +doko ___ Python tracker ___ ___ Python-bugs-list mailing

[issue26443] cross building extensions picks up host headers

2016-02-26 Thread Martin Hundebøll
New submission from Martin Hundebøll: When cross building python, the building of extensions is called with -I/usr/include and -L/usr/lib This makes some extensions fail to compile due to picking up inline assembly from host headers (e.g. _socket[1]). I have fixed this locally by applying