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 ronaldoussoren
Recipients Francois.Dion, Garen, Justin.Venus, Marc.Abramowitz, belopolsky, benjamin.peterson, danchr, dhduvall, dmalcolm, eric.snow, fche, glyph, hazmat, jbaker, jcea, jmcp, laca, lasizoillo, loewis, mjw, movement, neologix, pitrou, rhettinger, robert.kern, ronaldoussoren, samueljohn, scox, serverhorror, sirg3, twleung, wsanchez
Date 2012-08-29.07:23:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The obvious workaround w.r.t. dtrace not finding the preprocessor is to install the command-line tools for xcode, which you can do from Xcode's preferences.

something else to try (before installing the commandline tools): add $(dirname $(xcrun -find cpp)) to the search path of the shell:

bash$ PATH="${PATH}:$(dirname $(xcrun -find cpp))"

This adds the directory in the Xcode bundle that contains the command-line tools to the search path of the shell, and might make it possible for dtrace to find the preprocessor (depending on how dtrace is coded). If that works this trick could be added to the build process, we already do something similar to locate the compiler in the configure script.
Date User Action Args
2012-08-29 07:24:38ronaldoussorensetrecipients: + ronaldoussoren, loewis, rhettinger, jcea, belopolsky, pitrou, wsanchez, movement, benjamin.peterson, serverhorror, glyph, laca, twleung, jbaker, robert.kern, sirg3, danchr, dhduvall, dmalcolm, samueljohn, mjw, Garen, neologix, lasizoillo, fche, hazmat, eric.snow, jmcp, scox, Marc.Abramowitz, Justin.Venus, Francois.Dion
2012-08-29 07:24:05ronaldoussorensetmessageid: <>
2012-08-29 07:24:04ronaldoussorenlinkissue13405 messages
2012-08-29 07:23:59ronaldoussorencreate