Hi Soumyajyotii!

Thanks for working on this.

It is a big challenging for me to understand your question and what
context it is in. Did you do some code changes? Can you push them
somewhere so I can look at the changes you made, the command you ran
and the error message you get to have proper context?

Below it seems the server crashed when
debian/rules:override_dh_auto_test was executing. Your second question
about 'CMake configure stage' is a bit baffling, as you surely were
past the configure stage already in a previous run as
override_dh_auto_test ran.

Did you start from scratch or are you using
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/146
as the starting point?

On Wed, 14 Jan 2026 at 09:55, Soumyajyotii Ssarkar
<[email protected]> wrote:
>
> Hey Otto,
> I am actually currently working on it.
> I was last able to produce this error which I am currently trying to fix with 
> mariadb codebase, but I think its progress perhaps?
>
> # ERROR LOG 1 (initially I faced this):
> Server version: 11.8.5-MariaDB-4 from Debian source revision: 
> 2bb18a8cf1170b7c506b9c57640d8798a3b74298
> The information page at 
> https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/
> contains instructions to obtain a better version of the backtrace below.
> Following these instructions will help MariaDB developers provide a fix 
> quicker.
> Attempting backtrace. Include this in the bug report.
> (note: Retrieving this information may fail)
> Thread pointer: 0x0
> stack_bottom = 0x0 thread_stack 0x49000
> /home/soumyajyotii/build/mariadb-server/builddir/sql/mariadbd(my_print_stacktrace-0x36cf6292)
>  [0x421a4dac]
> Writing a core file...
> Working directory at 
> /home/soumyajyotii/build/mariadb-server/builddir/mysql-test/var/install.db
> Resource Limits (excludes unlimited resources):
> Limit                     Soft Limit           Hard Limit           Units
> Max stack size            8388608              unlimited            bytes
> Max processes             257230               257230               processes
> Max open files            1024                 1024                 files
> Max locked memory         8388608              8388608              bytes
> Max pending signals       257230               257230               signals
> Max msgqueue size         819200               819200               bytes
> Max nice priority         0                    0
> Max realtime priority     0                    0
> Core pattern: core
> Kernel version: Linux version 6.12.57+deb13-amd64 
> ([email protected]) (x86_64-linux-gnu-gcc-14 (Debian 14.2.0-19) 
> 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #1 SMP PREEMPT_DYNAMIC Debian 
> 6.12.57-1 (2025-11-05)
> make[1]: *** [debian/rules:162: override_dh_auto_test] Error 1
> make[1]: Leaving directory '/home/soumyajyotii/build/mariadb-server'
> make: *** [debian/rules:253: binary] Error 2
> dpkg-buildpackage: error: debian/rules binary subprocess failed with exit 
> status 2
>
>
>
> Currently the build is failing at the CMake configure stage because MariaDB 
> still expects a required core dependency to be present, even after all 
> related optional features have been explicitly disabled.
>
> So I am trying to figure it out and fix it.
>
> Your advice and guidance would be appreciated on how I could work more 
> closely with the MariaDB Community for the porting.
>
> Thank you,
> Soumyajyotii Ssarkar.

Reply via email to