Message280318
| 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 |
<1478623438.98.0.31306276097.issue21590@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
@Łukasz
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. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2016年11月08日 16:43:59 | cstratak | set | recipients:
+ cstratak, jcea, durin42, SilentGhost, dmalcolm, xmorel, cburroughs, lukasz.langa, python-dev, berker.peksag, bkabrda, koobs, benesch |
| 2016年11月08日 16:43:58 | cstratak | set | messageid: <1478623438.98.0.31306276097.issue21590@psf.upfronthosting.co.za> |
| 2016年11月08日 16:43:58 | cstratak | link | issue21590 messages |
| 2016年11月08日 16:43:58 | cstratak | create |
|