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 cstratak
Recipients SilentGhost, benesch, berker.peksag, bkabrda, cburroughs, cstratak, dmalcolm, durin42, jcea, koobs, lukasz.langa, python-dev, xmorel
Date 2016-11-08.16:43:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>

Dug a bit more to it.

Yes it is RPM specific for that case, in the sense that we create different subfolders for the debug and the normal(optimized) builds under the build/ dir, where the Include directory does not exist. the dtrace wrapper assumes that the directory already exists. The issue of course can be reproduced with any packaging system (or ways to compile python) that follow this approach, although I am not aware currently if this can happen or might be happening anywhere else.

By creating the directory (if it doesn't exist) at the Makefile rule for generating pydtrace_probes.h, this can be circumvented.

Attaching a patch that fixes this issue for consideration.
Date User Action Args
2016-11-08 16:43:59cstrataksetrecipients: + cstratak, jcea, durin42, SilentGhost, dmalcolm, xmorel, cburroughs, lukasz.langa, python-dev, berker.peksag, bkabrda, koobs, benesch
2016-11-08 16:43:58cstrataksetmessageid: <>
2016-11-08 16:43:58cstrataklinkissue21590 messages
2016-11-08 16:43:58cstratakcreate