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 jcea
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-27.18:12:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Samuel, the program complaining about not being able to find the C Preprocessor is the system "dtrace" executable. Looks like a dependency there.

To check this hypotesis, create a file called "a.d", with the following content:

provider test {
  probe abc(int);


and try to generate the header file with the following command:

dtrace -C -h -s a.d

If that command complains about being unable to find the C Preprocessor, well, you need a C Preprocessor.

If dtrace doesn't obey environment variables pointing to the preprocessor, that would be a dtrace bug. You could create a symbolic link to "clang" executable, but that would be an ugly hack.
Date User Action Args
2012-08-27 18:12:29jceasetrecipients: + jcea, loewis, rhettinger, ronaldoussoren, 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-27 18:12:28jceasetmessageid: <>
2012-08-27 18:12:28jcealinkissue13405 messages
2012-08-27 18:12:27jceacreate