<div dir="ltr">Hey Otto,<div>I am actually currently working on it.</div><div>I was last able to produce this error which I am currently trying to fix with mariadb codebase, but I think its progress perhaps?</div><div><br></div><div><b># ERROR LOG 1 (initially I faced this):</b><br>Server version: 11.8.5-MariaDB-4 from Debian source revision: 2bb18a8cf1170b7c506b9c57640d8798a3b74298<br>The information page at <a href="https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/">https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/</a><br>contains instructions to obtain a better version of the backtrace below.<br>Following these instructions will help MariaDB developers provide a fix quicker.<br>Attempting backtrace. Include this in the bug report.<br>(note: Retrieving this information may fail)<br>Thread pointer: 0x0<br>stack_bottom = 0x0 thread_stack 0x49000<br>/home/soumyajyotii/build/mariadb-server/builddir/sql/mariadbd(my_print_stacktrace-0x36cf6292) [0x421a4dac]<br>Writing a core file...<br>Working directory at /home/soumyajyotii/build/mariadb-server/builddir/mysql-test/var/install.db<br>Resource Limits (excludes unlimited resources):<br>Limit Soft Limit Hard Limit Units<br>Max stack size 8388608 unlimited bytes<br>Max processes 257230 257230 processes<br>Max open files 1024 1024 files<br>Max locked memory 8388608 8388608 bytes<br>Max pending signals 257230 257230 signals<br>Max msgqueue size 819200 819200 bytes<br>Max nice priority 0 0<br>Max realtime priority 0 0<br>Core pattern: core<br>Kernel version: Linux version 6.12.57+deb13-amd64 (<a href="mailto:debian-kernel@lists.debian.org">debian-kernel@lists.debian.org</a>) (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)<br>make[1]: *** [debian/rules:162: override_dh_auto_test] Error 1<br>make[1]: Leaving directory '/home/soumyajyotii/build/mariadb-server'<br>make: *** [debian/rules:253: binary] Error 2<br>dpkg-buildpackage: error: debian/rules binary subprocess failed with exit status 2<br></div><div><br></div><div><br></div><div><br></div><div>Currently the build is failing at the CMake <em style="">configure</em> stage because MariaDB still expects a required core dependency to be present, even after all related optional features have been explicitly disabled.</div><div><br></div><div>So I am trying to figure it out and fix it.</div><div><br></div><div>Your advice and guidance would be appreciated on how I could work more closely with the MariaDB Community for the porting.</div><div><br></div><div>Thank you,</div><div>Soumyajyotii Ssarkar.</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Wed, Jan 14, 2026 at 11:01 PM Otto Kekäläinen <<a href="mailto:otto@debian.org">otto@debian.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi!<br>
<br>
In December many expressed interest in porting MariaDB to hppa, but I<br>
didn't notice any comments on any of the bug report or MR or any other<br>
follow-up, so I guess perhaps people didn't have time for this after<br>
all..?<br>
<br>
<br>
> >>>> I am happy to take your patches, do additional testing and do uploads.<br>
> >>>> Unfortunately I can't do the actual port fixing myself as there is too<br>
> >>>> much work and the domain is something I am not strong in. My attempt<br>
> >>>> at fixes at <a href="https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/146" rel="noreferrer" target="_blank">https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/146</a><br>
> >>>> did get some progress, so if you want to take on this challenge, you<br>
> >>>> don't need to start from zero.<br>
> >>>><br>
> >>>> I also have good experiences of getting upstream to accept porting<br>
> >>>> related patches (e.g. <a href="https://github.com/MariaDB/server/pull/4480" rel="noreferrer" target="_blank">https://github.com/MariaDB/server/pull/4480</a>) so<br>
> >>>> if you fix this in Debian and submit patches upstream, you most likely<br>
> >>>> will get those fixes into MariaDB permanently for all users globally.<br>
> >>><br>
> >>> The first step should be disabling Java support on hppa. Since OpenJDK currently<br>
> >>> does not support hppa due to the stack growing from upwards, any packages that<br>
> >>> make use of Java won't work on hppa.<br>
> >>><br>
> >>> There is some work-in-progress port for OpenJDK on hppa that I worked on some<br>
> >>> years ago but I never finished the actual work. It might be a good idea to<br>
> >>> complete that work in the future though.<br>
> >><br>
> >><br>
> >> Sure, sounds like a great place to start? I will try to get it setup and disable the java functionality first, perhaps to try and get it running.<br>
> ><br>
> > Please start by reading the<br>
> > <a href="https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/146" rel="noreferrer" target="_blank">https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/146</a><br>
> > I mentioned in my original email, and the notes and comments in it. It<br>
> > will help you avoid doing things I already did, and there are also<br>
> > commands linked you can just copy-paste to get the build and test<br>
> > suite going on a porter box (or anywhere).<br>
> ><br>
> > Thanks for taking a stab at making this package build and pass tests in hppa!<br>
> ><br>
</blockquote></div>