On Thu, Jun 19, 2008 at 07:50:06AM -0700, Alan Coopersmith wrote: > John Birrell wrote: > > The reason why it is failing is because the CTF data generation for the > > kernel is currently opt-in rather than enabled by default. This was done to > > allow the early adopters a chance to try it before defaulting it to on (as > > it will be eventually). > > > > The only way that libdtrace can determine the type of uid_t on FreeBSD is > > to get the info from CTF in the kernel. Without that CTF, the library D > > script parse fails. > > > > Userland tracing isn't supported yet in FreeBSD, so the Xorg build is being > > a bit adventurous trying to use 'dtrace' in it's build simply because it is > > installed. > > Well, that's the GNU autoconf way - if you find a feature, you > use it. Is there a better test we should put in there to determine > if it's safe to use on FreeBSD or should we just add freebsd* to > darwin* in the OS matching patterns in the blacklist for now?
I suggest that Xorg does nothing. The FreeBSD port needs to have the without dtrace config otion set in the configure definition. This is easy to do. I'm not a ports committer, so I can't do it myself. I assumed that because this was mentioned in a topic on ports@ that it would be done. -- John Birrell _______________________________________________ dtrace-discuss mailing list [email protected]
