Hi Adrian,
>Could you point me to the actual error message so I know how the reproducer
>looks like?
sure: it’s the
Total failed: 3 (3 unexpected)
in the build log, and before that:
FAIL ../../debian/mtest.t:mtest-external
Description:
Minitest: can run an external utility and return
test timed out (limit of 3 seconds)
unexpected exit status 9 (signal 9), expected 0
unexpected stdout - got too little output
wanted:
bar
baz
got:
bar
>I can, indeed, just test whether mksh works on a real Amiga
>68060 which I have running for this purpose.
The trick here is that the faulty binary is not included in
the .deb package thanks to the testsuite failure, so it’s
not all that easy.
Recompiling the .dsc would trigger it though (expect that to
take a couple of hours, perhaps a day…).
You *might* be able to trigger it with:
$ apt-get source mksh
$ cd mksh-*/
$ env LC_ALL=C HAVE_CAN_WALL=0 HAVE_LIBUTIL_H=0 CC=klcc \
HAVE_CAN_FSTACKPROTECTORSTRONG=0 HAVE_CAN_FSTACKPROTECTORALL=0 \
CFLAGS='-fstack-protector-strong -Wformat -Werror=format-security -Wall
-Wextra -g -fno-stack-protector -Os' \
CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2 -DMKSH_BINSHPOSIX
-DMKSH_BINSHREDUCED -DMKSH_SMALL -DMKSH_SMALL_BUT_FAST' \
LDFLAGS='-Wl,-z,relro -Wl,-z,now -Wl,--as-needed' \
LDSTATIC=-static LIBS= sh Build.sh -r && \
perl check.pl -s debian/mtest.t -p ./mksh -v
This should do roughly the same as the package build does in that
place, although I’m not sure I caught all exports.
Thanks,
//mirabilos
--
When he found out that the m68k port was in a pretty bad shape, he did
not, like many before him, shrug and move on; instead, he took it upon
himself to start compiling things, just so he could compile his shell.
How's that for dedication. -- Wouter, about my Debian/m68k revival
