The unifdef testsuite has been failing sometimes for years with
_FORTIFY_SOURCE in a non-obvious way, where glibc's fgets will return
\0 w/ n=1.
I'd found marxin's PR for this years ago and apparently completely forgot
about it (nor did I backport the patch into Gentoo at the time, as
I didn't maintain it, and I was fairly new then).
Backport marxin's patch from 2022 accordingly. Thanks to Ben Beasley
poking me on the upstream PR (19) which made me look at all of this
again.
Bug: https://gcc.gnu.org/PR120205
Bug: https://github.com/fanf2/unifdef/pull/15
Bug: https://github.com/fanf2/unifdef/pull/19
Closes: https://bugs.gentoo.org/836698
Signed-off-by: Sam James <sam@gentoo.org>
As of >=sys-libs/pam-1.7.0 (upstream commit 941bfc1de4c8d4963c8b9d63d32fed391f1476c8),
pam's .pc files expect proper includes in consumers with the <security/*>
namespace. Adapt to that.
Closes: https://bugs.gentoo.org/948461
Signed-off-by: Sam James <sam@gentoo.org>
Not sure if negril will want to fix this another way, but let's do
the quick-n-easy thing for now.
Closes: https://bugs.gentoo.org/955687
Signed-off-by: Sam James <sam@gentoo.org>
In...
commit e620abbc937619f3d69896ff4d7ace2696bc0c93
Author: Manuel Rüger <mrueg@gentoo.org>
Date: Wed Jul 10 09:46:16 2013 +0000
Non-maintainer commit: Add support for fglrx (AMD ADL). Fix desktop file. See bug #475568
(Portage version: 2.1.12.13/cvs/Linux x86_64, signed Manifest commit with key )
... .in gets changed to .ini, which seems weird.
The line itself goes back to:
commit 3255c2e57a7c24147aa50ca7cf9603211e790e9a
Author: Robin H. Johnson <robbat2@gentoo.org>
Date: Sun Jul 15 07:44:37 2007 +0000
Bug #163057 - compile fix for zlib'd pciutils. Also fix compile on ppc for in/out/ioperm usage.
(Portage version: 2.1.3_rc8)
Back then, it was:
+ if [ "${ARCH/64}" == "ppc" ]; then
It changed to the current arch check with:
commit 5cb6622ff2a100c12d020f1d03bf25ac9670e072
Author: Mike Frysinger <vapier@gentoo.org>
Date: Wed Jan 25 02:17:34 2012 +0000
Migrate to EAPI=4, fix build with newer automake with patch from upstream, add USE=static-libs support, and add USE=ddcpci to control the setuid binary.
(Portage version: 2.2.0_alpha84/cvs/Linux x86_64)
In any case, let's just drop it and see what happens. Especially given
it's been broken for non-amd64 + x86 (which is the case it's supposed
to help with) for several months at the very least.
Closes: https://bugs.gentoo.org/949965
Signed-off-by: Sam James <sam@gentoo.org>
Newer egl-wayland started using linux-drm-syncobj-v1 protocol that
was added only in >=1.34, and upstream's build system doesn't do a
version check so missed that.
Haven't actually tested building with gone-from-the-tree 1.34 though,
but it should work in theory looking at commits.
https://forums.gentoo.org/viewtopic-p-8861372.html#8861372
Thanks-to: Andreas Sturmlechner <asturm@gentoo.org>
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Sam James
Michael Kochera
Mike Pagano
Ionen Wolkens
Alfredo Tupone
Andreas K. Hüttel
Andreas Sturmlechner
Michał Górny