Leonardo Taccari <leot%NetBSD.org@localhost> writes:
> Index: Makefile
> ===================================================================
> RCS file: /cvsroot/pkgsrc/lang/ruby200-base/Makefile,v
> retrieving revision 1.21
> diff -u -p -r1.21 Makefile
> --- Makefile 14 Oct 2015 18:36:06 -0000 1.21
> +++ Makefile 20 Dec 2015 16:01:39 -0000
> @@ -69,6 +69,12 @@ CONFIGURE_ENV+= OBJCOPY=:
> CONFIGURE_ENV+= ac_cv_func_getgrnam_r=no
> .endif
>
> +.if ${OPSYS} == "NetBSD"
> +# while dtrace is correctly recognised during the configure phase it fails
> +# early during the build phase when linking miniruby.
> +CONFIGURE_ARGS+= --disable-dtrace
> +.endif
> +
> .if ${OPSYS} == "OpenBSD" || ${OPSYS} == "Bitrig"
> USE_TOOLS+= bash
> CONFIG_SHELL= ${TOOLS_PATH.bash}
Is enough of dtrace always built with NetBSD for using dtrace to make
sense (vs being an option)? Generally, pkgsrc tries to avoid
compile-time detection in favor of requiring features or hiding them
(via bl3).
But, we don't really have a good way to deal with things that are
optional in the base system. It seems with dtrace there are some MK
variables to set in the build, rather than it being standard.
So I wonder if you are building on a stock netbsd-7 machine, or if
you've enabled dtrace specifically.
Attachment:
signature.asc
Description: PGP signature