https://bugzilla.novell.com/show_bug.cgi?id=445074
User [EMAIL PROTECTED] added comment https://bugzilla.novell.com/show_bug.cgi?id=445074#c6 --- Comment #6 from Andreas Färber <[EMAIL PROTECTED]> 2008-11-29 02:55:17 MST --- Yes, that's what Rodrigo has inquired me about. Possible solutions are: a) use --disable-dtrace on the build bot b) revert the commit that enabled DTrace by default based on platform I believe it is buggy since it does not seem to check for OS version anyway - Solaris 9 and earlier do not have it, nor do Mac OS X v10.4 and earlier. c) check for `dtrace -V` version output We'd need to know the problematic DTrace versions, and the build log doesn't show that. d) try to do `dtrace -h ...` during configure Could use a dummy provider file or the real one and check return value. e) provide alternative header file generation From my view, e) is not a good option since newer versions of dtrace are easily obtainable and thus not worth the duplicate effort on our part. If you'd ssh onto your build bot and tell me the `dtrace -V` output, as requested before, I could easily supply a patch that greps for the problematic version(s) (1.0.x? 1.1.x?) and sets has_dtrace=no in that case, so that DTrace does not get enabled for the build. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. _______________________________________________ mono-bugs maillist - mono-bugs@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-bugs
