We don't yet have newer cmocka packaged (partly because I was worried
about breakage), but backport a fix which looks like it should help with it.
Also, add an extra test dep on uid_wrapper.
Signed-off-by: Sam James <sam@gentoo.org>
config.h:1:1: error: expected identifier or ‘(’ before ‘-’ token
1 | -e #ifndef __VK_CONFIG_H
This is just... dandy... I too love unix command flags echo'ed into my
headers...
It uses echo -e to a header, which breaks on non-bash shells and is
generally a problem.
Closes: https://bugs.gentoo.org/886069
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
This package is absolutely horrible. It has the world's worst homebrew
"configure" script, which fails but doesn't *error out* with
-Wimplicit-int as a compiler default error, and also has:
config.h:1:1: error: expected identifier or ‘(’ before ‘-’ token
1 | -e #ifndef __VK_CONFIG_H
which is just... dandy... I too love unix command flags echo'ed into my
headers...
It's a wreck but we can at least detect when it cannot compile anything
and abort with a clearer message.
Bug: https://bugs.gentoo.org/900398
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
With --buildpkgonly the account packages aren't needed, so don't force
them to be installed yet. An RDEPEND is fine.
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
In commit 73937e86b9, a version bump was
applied, and a patch file in FILESDIR which was applied to the old
version was "rebased" against the new release and applied in-place for
both the old and new versions.
Result: stable ebuild does not compile because patch doesn't match.
Fixes: 73937e86b9
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
The python Limited API allows you to compile a native extension once for
e.g. python 3.8, create a wheel package, and then install that on any
version of python 3.8+. This is inherently non-useful to distros, which
compile the extensions for each build regardless.
The Limited API is slower than the internal API, and benefits nothing at
all for our use case. But shiboken defaults to creating one. Manually
pass the option to disable it.
The Limited API builds of shiboken also have LTO issues that the regular
builds do not. Odd. See comments at https://bugreports.qt.io/browse/PYSIDE-2619
(Note that there are other LTO issues with shiboken which are fixed in
git dev, so we can't remove filter-lto yet.)
Bug: https://bugs.gentoo.org/925479
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
This is why sed is bad. The sed didn't apply, even in the first edition
of the ebuild that it was introduced in, because it used incorrect sed
syntax. Because it was a sed, this fact escaped all notice even though
it never ever worked.
Just use a patch. Patches always either apply or fail, they aren't prone
to silently doing *nothing*.
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>