Bug#924891: glibc: FTBFS: /<<PKGBUILDDIR>>/build-tree/amd64-libc/conform/UNIX98/ndbm.h/scratch/ndbm.h-test.c:1:10: fatal error: ndbm.h: No such file or directory
- To: Lucas Nussbaum <lucas@debian.org>
- Cc: 924891@bugs.debian.org
- Subject: Bug#924891: glibc: FTBFS: /<<PKGBUILDDIR>>/build-tree/amd64-libc/conform/UNIX98/ndbm.h/scratch/ndbm.h-test.c:1:10: fatal error: ndbm.h: No such file or directory
- From: Florian Weimer <fw@deneb.enyo.de>
- Date: Fri, 22 Mar 2019 17:30:42 +0100
- Message-id: <[🔎] 87h8buna6l.fsf@mid.deneb.enyo.de>
- Reply-to: Florian Weimer <fw@deneb.enyo.de>, 924891@bugs.debian.org
- In-reply-to: <20190317175722.qgsm6uvonexs35ot@xanadu.blop.info> (Lucas Nussbaum's message of "Sun, 17 Mar 2019 18:57:23 +0100")
- References: <20190317175722.qgsm6uvonexs35ot@xanadu.blop.info> <20190317175722.qgsm6uvonexs35ot@xanadu.blop.info>
> 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.
I believe the actual test failure is tst-pkey.
Presumably, this rebuild was performed on some Xeon SP CPU. Do you
know which model? Do you have any information about the kernel and
hypervisor used?
32-bit protection key support has had issues from time to time.
Thanks.
Reply to: