Hi,

duma is FTBFS on Hurd because a self test fails. https://buildd.debian.org/status/fetch.php?pkg=duma&arch=hurd-i386&ver=2.5.21-2&stamp=1633376424&raw=0
<https://buildd.debian.org/status/fetch.php?pkg=duma&arch=hurd-i386&ver=2.5.21-2&stamp=1633376424&raw=0>

That part of the build log reads

.
Testing DUMA (static library):
./dumatest
GNUmakefile:373: recipe for target 'test' failed
make[1]: *** [test] Killed

dh_auto_test: error: make -j1 test returned exit code 2
debian/rules:8: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 255
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2

I'm wondering what Error 255 means on Hurd, and whether this could be anything to do with threading?
Also it might be useful to know the output of "uname -s" is on Hurd, as the makefile branches on the value.

Cheers,
Peter

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, Oct 9, 2021 at 10:41 AM Peter <peter@pblackman.plus.com> wrote:

...
Also it might be useful to know the output of "uname -s" is on Hurd, as the makefile branches on the value.

jwalton@hurd-x86:~$ uname -s
GNU
jwalton@hurd-x86:~$ uname -o
GNU
jwalton@hurd-x86:~$ uname -a
GNU hurd-x86 0.9 GNU-Mach 1.8+git20210404-486/Hurd-0.9 i686-AT386 GNU

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Peter, le sam. 09 oct. 2021 15:33:22 +0100, a ecrit:

./dumatest
GNUmakefile:373: recipe for target 'test' failed
make[1]: *** [test] Killed

dh_auto_test: error: make -j1 test returned exit code 2
debian/rules:8: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 255
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2

I'm wondering what Error 255 means on Hurd,

Well, I don't think there is anything hurd-specific here, since it's
just the value returned by the program.

Note that there is the exodar porter box which is available for testing.

Samuel

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 09/10/2021 16:39, Jeffrey Walton wrote:

On Sat, Oct 9, 2021 at 10:41 AM Peter <peter@pblackman.plus.com> wrote:

...
Also it might be useful to know the output of "uname -s" is on Hurd, as the makefile branches on the value.

jwalton@hurd-x86:~$ uname -s
GNU
jwalton@hurd-x86:~$ uname -o
GNU
jwalton@hurd-x86:~$ uname -a
GNU hurd-x86 0.9 GNU-Mach 1.8+git20210404-486/Hurd-0.9 i686-AT386 GNU

Thanks!

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 10/10/2021 01:26, Samuel Thibault wrote:

Peter, le sam. 09 oct. 2021 15:33:22 +0100, a ecrit:

./dumatest
GNUmakefile:373: recipe for target 'test' failed
make[1]: *** [test] Killed

dh_auto_test: error: make -j1 test returned exit code 2
debian/rules:8: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 255
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2

I'm wondering what Error 255 means on Hurd,

Well, I don't think there is anything hurd-specific here, since it's
just the value returned by the program.

Note that there is the exodar porter box which is available for testing.

Samuel

Thanks Samuel,

I was hoping there might be a quick fix to the makefile for this,
but realise now its probably that the package is OS specific (like valgrind).
I have found several exit (-1) in the source code that would result in a 255, but its odd that stderr seems silent.

Cheers,
Peter

P.S.
Just curious. Has anyone ever tried using electric-fence on Hurd?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)