Re: Bug#916052: alsa-oss FTBFS with glibc 2.28

[Takashi Sakamoto <o-takashi@sakamocchi.jp>]

Hi,

On Wed, Dec 12, 2018 at 02:37:43PM +0100, Elimar Riesebieter wrote:
> Control: forwarded -1 alsa-devel@alsa-project.org
> 
> 
> Hi,
> 
> could you please investigate? It seems as alsa-oss doesn't built
> with glibc 2.28.
> 
> Thanks in advance
> Elimar
> -- 
>   Learned men are the cisterns of knowledge,
>   not the fountainheads ;-)

> Date: Sun, 09 Dec 2018 19:10:03 +0200
> From: Adrian Bunk <bunk@debian.org>
> To: Debian Bug Tracking System <submit@bugs.debian.org>
> Subject: Bug#916052: alsa-oss FTBFS with glibc 2.28
> X-Mailer: reportbug 7.5.0
> 
> Source: alsa-oss
> Version: 1.1.6-1
> Severity: serious
> Tags: ftbfs
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/alsa-oss.html
> 
> ...
> In file included from alsa-oss.c:736:
> stdioemu.c:40:10: fatal error: libio.h: No such file or directory
>  #include <libio.h>
>           ^~~~~~~~~
> compilation terminated.
> make[2]: *** [Makefile:517: alsa-oss.lo] Error 1
> 

In glibc upstream, libio/libio.h had been deprecated for applications and
became internal header in its v2.28 release. We can see below message in
its release note[1].

```
* The nonstandard header files <libio.h> and <_G_config.h> are no longer
  installed.  Software that was using either header should be updated to
  use standard <stdio.h> interfaces instead.
```

I posted PR to fix the FTBFS into github.com repository[1]. (In last month
we introduced github service to our workload for reviewing/merging tasks
just for userspace stuffs.)

In next release (v1.1.7), the fix will be merged and released.

[1] https://www.sourceware.org/ml/libc-alpha/2018-08/msg00003.html
[2] https://github.com/alsa-project/alsa-oss/pull/1


Thanks

Takashi Sakamoto