> > It is possible that glibc may have something to do with this? > > (note that gcc-14 has not been updated for trixie). > > Yes, this is due to this commit [2] that got backported in order to > support the linux-libc-dev package provided by the trixie-backport > kernel [2]: > > commit 419245719ccbc7dad6a97f24465e7f09c090327a > Author: DJ Delorie <[email protected]> > Date: Mon Jan 26 22:24:42 2026 -0500 > > include: isolate __O_CLOEXEC flag for sys/mount.h and fcntl.h > > Including sys/mount.h should not implicitly include fcntl.h > as that causes namespace pollution and conflicts with kernel > headers. It only needs O_CLOEXEC for OPEN_TREE_CLOEXEC > (although it shouldn't need that, but it's defined that way) > so we provide that define (via a private version) separately. > > Reviewed-by: Adhemerval Zanella <[email protected]> > Tested-by: Florian Weimer <[email protected]> > > That means that <fcntl.h> is not included anymore when including > <sys/mount.h>. POSIX is clear that open() is defined in <fcntl.h>, so > while this is unfortunate to introduce a bug in trixie, the bug is > really on the ascdc package.
Thanks a lot for the quick reply. I'm concerned about the stability of stable. So far I've found already four packages failing in a similar way, and some of the bugs were already fixed and archived: ascdc_0.3-15.1 #1136759 asmixer_0.5-16.1 #1136761 oar_2.6.1-1 #1136780 switchsh_0~20070801-5 #1136783 Did anybody try to estimate how many packages would be affected in trixie before making the glibc change? We probably can fix those for the next point release, but: What if the number of affected packages had been 50 or 100? If we want to keep the promise that stable is buildable from source, what we are currently doing is not working. Note that I'm not asking you to fix any of the new problems, I just wanted to raise awareness about the stability of stable. (On the positive side, Debian 13.7 fixed at least 24 FTBFS issues, but that's mainly because we finally fixed python3.13, which broke most of those issues in the previous point release). Thanks.
