Bug#954494: proftpd-mod-counter: FTBFS: conf.h:57:11: fatal error: stropts.h: No such file or directory

[Lucas Nussbaum]

Source: proftpd-mod-counter
Version: 0.6.2-1
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):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> DESTDIR=/<<PKGBUILDDIR>>/debian/proftpd-mod-counter prxs -c mod_counter.c
> libtool --mode=compile gcc  -DLINUX -g2 -g -O2 -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -fno-omit-frame-pointer -Werror=implicit-function-declaration -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_counter.c
> libtool: compile:  gcc -DLINUX -g2 -g -O2 -fdebug-prefix-map=/build/proftpd-dfsg-3rBFSi/proftpd-dfsg-1.3.6c=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -fno-omit-frame-pointer -Werror=implicit-function-declaration -DPR_SHARED_MODULE -I. -I/usr/include/proftpd -c mod_counter.c  -fPIC -DPIC -o .libs/mod_counter.o
> In file included from mod_counter.c:28:
> /usr/include/proftpd/conf.h:57:11: fatal error: stropts.h: No such file or directory
>    57 | # include <stropts.h>
>       |           ^~~~~~~~~~~
> compilation terminated.
> prxs: error executing command (1)
> make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/proftpd-mod-counter_0.6.2-1_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.