Nick Alcock via DTrace-devel <dtrace-devel@oss.oracle.com> writes:

> On 10 Feb 2026, Kris Van Hees via DTrace-devel outgrape:
>
>> Packaging configuration files for Debian are provided in dists/debian.
>
> Nice! Seems to work, even on Debian stable (I was sure I'd need at least
> testing, but no!).
>
> [...]
>> diff --git a/dists/debian/patches/debian-configure.patch b/dists/debian/patches/debian-configure.patch
>> new file mode 100644
>> index 00000000..d4a89bb9
>> --- /dev/null
>> +++ b/dists/debian/patches/debian-configure.patch
>> @@ -0,0 +1,17 @@
>> +Description: issue a warning for unknown configure options
>> + The Debian build system specifies configure options that are not known to
>> + the DTrace configure script.  They should not cause the configure script
>> + to abort.
>> +--- dtrace-2.0.4.orig/configure
>> ++++ dtrace-2.0.4/configure
>> +@@ -172,8 +172,7 @@ for option in "$@"; do
>> +         HAVE_VALGRIND=*) write_config_var VALGRIND "$option";;
>> +         HAVE_BPFV3=*) write_config_var BPFV3 "$option";;
>> +         HAVE_BPFMASM=*) write_config_var BPFMASM "$option";;
>> +-        *) echo "Unknown option $option" >&2
>> +-           exit 1;;
>> ++        *) echo "Unknown option $option" >&2;;
>> +     esac
>> + done
>
> I assumed you could just stuff an || true in there, but this is being
> invoked by dh_auto_configure, so that option isn't available (plus, of
> course, if there's an actual error other than unknown args, we don't
> want to fail).
>
> Maybe we should just not exit with exitcode 1 on unknown configure
> options, only IIRC Gentoo actually wants us to. This may be the best we
> can do.

I really doubt this is the first / only package for Debian where there's
a non-autoconf configure script.

The real issue here is letting whatever Debian machinery that calls
configure think it is autoconf. ebuilds do the same, by default econf
will pass things assuming it's autoconf.

I'm sure there's a way to override that?

>
>> diff --git a/dists/debian/patches/debian-interpreter-paths.patch b/dists/debian/patches/debian-interpreter-paths.patch
>> new file mode 100644
>> index 00000000..58bea538
>> --- /dev/null
>> +++ b/dists/debian/patches/debian-interpreter-paths.patch
>> @@ -0,0 +1,107 @@
>> +Description: fix interpreter paths in tests
>> + Lintian prefers /bin/bash and /bin/sed over /usr/bin/bash and /usr/bin/sed.
>
> Honestly this one I think we should do upstream. I always thought that
> /bin/bash is universal and /usr/bin/bash less so.
>

Yes.

> [...]

sam