Date: Mon, 9 Jun 2014 19:40:07 +0100 From: "Sevan / Venture37" <venture37@gmail.com> To: Mark Johnston <markj@freebsd.org> Cc: "freebsd-dtrace@freebsd.org" <freebsd-dtrace@freebsd.org> Subject: Re: DTrace probes for python 2.7.7 Message-ID: <CA%2BU3Mf4PZuwYwyed50Swza%2BQdsBFtTe5=q6_ZnpKyGs67k=jbg@mail.gmail.com> In-Reply-To: <CAMw1wOzE9An3Yz9XJh4xezoGk_UMJAxS=nJdj5Z4UquvverOgw@mail.gmail.com> References: <CA%2BU3Mf7_t3GuRMS0YicRb03ti56LHg_DD=iC=%2BD_wEj2SPNwyg@mail.gmail.com> <CA%2BU3Mf4ojD08wsWvRDkRDBmnk=eoJZCOD21hAMx1BC14_Kp5ZQ@mail.gmail.com> <CA%2BU3Mf7WJbGbqEAF7Zm77TYDAtSKbuU2pq=YwR=obtnfupLtYQ@mail.gmail.com> <CAMw1wOzE9An3Yz9XJh4xezoGk_UMJAxS=nJdj5Z4UquvverOgw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9 June 2014 19:28, Mark Johnston <markj@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BU3Mf4PZuwYwyed50Swza%2BQdsBFtTe5=q6_ZnpKyGs67k=jbg>