Re: [PATCH v2] Bump up the version to 2.0.4

Eugene Loh <[email protected]>
Newsgroups dev.linux.lists.dtrace
Message-ID <[email protected]>
Sorry for the duplicate...  this already got sent out.

On 10/27/25 14:25, [email protected] wrote:
> From: Eugene Loh <[email protected]>
>
> Note that test/unittest/preprocessor/tst.predefined.sh checks that the
> __SUNW_D_VERSION preprocessor symbol is consistent with the "dtrace -vV"
> message, and both of them simply use the last entry of versions.list and
> therefore will be consistent for in-tree builds.
>
> When RPM packages are built from the .spec file, however, _DT_VERSION,
> used for the "dtrace -vV" "This is" message, comes from the .spec file.
>
> Append a 2.0.4 entry to versions.list.
>
> Remove the VERSION=%{version} from dtrace.spec build's make line, so
> that the version of the implementation is defined by the source code
> itself.  The version in the spec file should be only the version of the
> packaging.
>
> Signed-off-by: Eugene Loh <[email protected]>
> ---
>   dtrace.spec             | 3 +--
>   libdtrace/versions.list | 1 +
>   2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/dtrace.spec b/dtrace.spec
> index a4f3ed774..e94025472 100644
> --- a/dtrace.spec
> +++ b/dtrace.spec
> @@ -131,8 +131,7 @@ it always tests the installed DTrace.
>   %setup -q
>   
>   %build
> -make -j $(getconf _NPROCESSORS_ONLN) VERSION=%{version} \
> -	%{bpfc} %{maybe_use_fuse2}
> +make -j $(getconf _NPROCESSORS_ONLN) %{bpfc} %{maybe_use_fuse2}
>   
>   # Force off debuginfo splitting.  We have no debuginfo in dtrace proper,
>   # and the testsuite requires debuginfo for proper operation.
> diff --git a/libdtrace/versions.list b/libdtrace/versions.list
> index 8986d2007..8d858f0bd 100644
> --- a/libdtrace/versions.list
> +++ b/libdtrace/versions.list
> @@ -65,3 +65,4 @@
>   2.0.1	D API 2.0.1 Linux (BPF)
>   2.0.2	D API 2.0.2 Linux (BPF)
>   2.0.3	D API 2.0.3 Linux (BPF)
> +2.0.4	D API 2.0.4 Linux (BPF)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.