Bug#963350: slashem: FTBFS: /bin/sh: 1: col: not found

Lucas Nussbaum lucas at debian.org
Sun Jun 21 21:13:26 BST 2020


Source: slashem
Version: 0.0.7E7F3-9
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[4]: Entering directory '/<<PKGBUILDDIR>>/src'
> make[4]: '../include/date.h' is up to date.
> make[4]: Leaving directory '/<<PKGBUILDDIR>>/src'
> cc -DDEBIAN_GTK -g -O2 -fomit-frame-pointer -fstack-protector --param=ssp-buffer-size=4 -I../include -I/usr/X11R6/include -Wdate-time -D_FORTIFY_SOURCE=2  -c -o recover.o recover.c
> recover.c: In function ‘main’:
> recover.c:114:10: warning: ignoring return value of ‘setgid’, declared with attribute warn_unused_result [-Wunused-result]
>   114 |   (void) setgid(getgid());
>       |          ^~~~~~~~~~~~~~~~
> recover.c:115:10: warning: ignoring return value of ‘setuid’, declared with attribute warn_unused_result [-Wunused-result]
>   115 |   (void) setuid(getuid());
>       |          ^~~~~~~~~~~~~~~~
> recover.c: In function ‘restore_savefile’:
> recover.c:308:5: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
>   308 |     write(sfd, (genericptr_t) &levc, sizeof(levc));
>       |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> cc -L/usr/X11R6/lib -Wl,-z,relro -o recover recover.o 
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/util'
> ( cd doc ; /usr/bin/make Guidebook )
> make[3]: Entering directory '/<<PKGBUILDDIR>>/doc'
> tbl tmac.n Guidebook.mn | nroff | col -bx > Guidebook
> /bin/sh: 1: col: not found
> make[3]: *** [Makefile:40: Guidebook] Error 127

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/slashem_0.0.7E7F3-9_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



More information about the Pkg-games-devel mailing list