DTrace probes for python 2.7.7

[Sevan / Venture37]

On 9 June 2014 19:28, Mark Johnston <markj at freebsd.org> wrote:
> This is probably because the build is running dtrace -G without the
> dtrace kernel modules loaded. This shouldn't be a problem, but
> currently is because dtrace(1) parses the scripts in /usr/lib/dtrace
> and errors out if dtrace isn't available in the kernel. Things like
> "#pragma depends_on" don't work, and there seem to be bugs in the
> error reporting of libdtrace; one ends up with the error messages
> above.
>
> I'd like to fix this by changing dtrace -G to not process scripts in
> the libdir, but I'm not yet sure what the implications of this are. I
> will ask on the dtrace-discuss list soon.
>
> In the meantime, a somewhat unsatisfactory workaround would be to just
> kldload dtraceall before starting the build.
>
> -Mark

Indeed, that was it, with dtraceall module loaded on r266655 VM's,
everything fails with the same error now.

"dtrace: failed to compile script Include/pydtrace.d: line 26: typedef
redeclared: __uint8_t"


Sevan