Testing period for 0.20.0; feature-freeze

[davmac314]

The current state of the main branch is undergoing testing over the next few days and, if no issues are discovered, the 0.20.0 release will be issued. This is intended to be the final beta release.

Any testing that can be performed is appreciated!

From this point, no significant new features will be accepted to the main branch, until 1.0 is released. Any exception to this needs prior approval from myself.

[softexpert]

Hello,

Trying to build using a slightly modified PKGBUILD (just getting the latest source from the repo instead of the latest tagged source) of the official Artix package, I get this error:

❯ makepkg
==> Making package: dinit 0.20.0-0.1 (mer. 05 nov. 2025 08:32:14)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating dinit git repo...
  -> Updating alpm-hooks git repo...
  -> Found dinit-init
==> Validating source files with sha256sums...
    dinit ... Skipped
    alpm-hooks ... Passed
    dinit-init ... Passed
==> Extracting sources...
  -> Creating working copy of dinit git repo...
Reset branch 'makepkg'
  -> Creating working copy of alpm-hooks git repo...
Reset branch 'makepkg'
==> Removing existing $pkgdir/ directory...
==> Starting build()...
make: Entering directory '/home/user/Private/git/ARTIX/dinit/src/dinit'
*** Found auto-configuration script for OS: Linux
Checking C++ compiler...
  ... g++
Checking whether "g++" is a working C++ compiler...
  ... Yes.
Checking whether "-lcap" is accepted as a link-time option...
  ... Yes.
Checking whether header "linux/ioprio.h" is available...
  ... Yes.
Checking whether "-fsanitize=address,undefined" is accepted as an option for both compiling and linking...
  ... Yes.
Creating mconfig...
../configure: line 700: LDFLAGS_MK: unbound variable
make: *** [Makefile:31: mconfig] Error 1
make: Leaving directory '/home/user/Private/git/ARTIX/dinit/src/dinit'
==> ERROR: A failure occurred in build().
    Aborting...

However, running make directly inside the /home/user/Private/git/ARTIX/dinit/src/dinit directory will build the binaries (/home/user/Private/git/ARTIX/dinit is the root path of the package I'm building).

I even tried to explicitly set AUTO_LDFLAGS to true, but the same error occurs.
There is a clear difference in the behavior of make when used in PKGBUILD, when comparing to running it directly in the source folder.

Could there be another variable that needs to be explicitly set?

[davmac314]

Thanks for reporting this - can you try with the latest commit, b2bb67a ?

[softexpert]

Hi Davin,

The package builds correctly with the commit b2bb67a.
Thank you for the quick fix!

[softexpert]

Simple curiosity: in the build trace, there is a warning about an argument value exceeding the maximum object size - could this become a potential error?

/usr/include/c++/15.2.1/new: In member function ‘allocate’:
/usr/include/c++/15.2.1/new:158:26: note: in a call to allocation function ‘operator new []’ declared here
  158 | _GLIBCXX_NODISCARD void* operator new[](std::size_t, const std::nothrow_t&)
      |                          ^
In member function ‘change_capacity’,
    inlined from ‘ensure_capacity’ at ../dasynq/include/dasynq/svec.h:151:31,
    inlined from ‘reserve’ at ../dasynq/include/dasynq/svec.h:253:29,
    inlined from ‘allocate’ at ../dasynq/include/dasynq/daryheap.h:222:33,
    inlined from ‘add_timer_nolock’ at ../dasynq/include/dasynq/timerbase.h:475:46,
    inlined from ‘register_timer’ at ../dasynq/include/dasynq.h:1045:39,
    inlined from ‘add_timer’ at ../dasynq/include/dasynq.h:2283:29,
    inlined from ‘__ct_base ’ at baseproc-service.cc:342:28:
../dasynq/include/dasynq/svec.h:113:32: warning: argument 1 value ‘18446744073709551600’ exceeds maximum object size 9223372036854775807 [-Walloc-size-larger-than=]
  113 |         T *new_storage = (T *)(new (std::nothrow) char[c * sizeof(T)]);
      |                                ^
/usr/include/c++/15.2.1/new: In member function ‘__ct_base ’:

[davmac314]

I'm confident that's a false positive. The warning is actually supposed to be suppressed, so it's strange that you're getting it.

[softexpert]

I was able to install the package(s) built from the official Artix PKGBUILD (modified to retrieve the source from the master branch and to take into account the renaming of dinit-check from dinitcheck).

Once restarted, it works perfectly fine.