[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#954520: yiyantang: FTBFS: setty.c:31:10: fatal error: stropts.h: No such file or directory



Source: yiyantang
Version: 0.7.0-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

This is most likely due to the upgrade to glibc 2.30. 
>From https://lists.gnu.org/archive/html/info-gnu/2019-08/msg00000.html:
> * The obsolete and never-implemented XSI STREAMS header files <stropts.h>
>   and <sys/stropts.h> have been removed.

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include     -DG_LOG_DOMAIN=\"yyt\"     -I../intl -I../intl  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -c setty.c
> setty.c:31:10: fatal error: stropts.h: No such file or directory
>    31 | #include <stropts.h>
>       |          ^~~~~~~~~~~
> compilation terminated.
> make[3]: *** [Makefile:201: setty.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/yiyantang_0.7.0-5_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.


Reply to: