- remove DOCS_EXTRA_ARGS: it causes too many problems
with "unexpected arguments" and it is not used anyway
- fix the append_deps function: apperently I messed up
somewhere and all deps but the first got ignored
- remove the check_deps function: it is not required
and is causing more problems at the moment (did the python
eclasses change the way they handle this function?)
Package-Manager: Portage-2.3.98, Repoman-2.3.22
Signed-off-by: Andrew Ammerlaan <andrewammerlaan@riseup.net>
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
A plugin to minify HTML and/or JS files
Package-Manager: Portage-2.3.98, Repoman-2.3.22
Signed-off-by: Andrew Ammerlaan <andrewammerlaan@riseup.net>
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
EVBACKEND_LINUXAIO was added to libev-4.24
EVBACKEND_IOURING was added in libev-4.31
```
src/gevent/libev/corecext.c: In function '__pyx_pymod_exec_corecext':
src/gevent/libev/corecext.c:24279:36: error: 'EVBACKEND_LINUXAIO' undeclared (first use in this function)
24279 | __pyx_t_1 = __Pyx_PyInt_From_int(EVBACKEND_LINUXAIO); if (unlikely(!__pyx_t_1)) __PYX_ERR(0, 113, __pyx_L1_error)
| ^~~~~~~~~~~~~~~~~~
src/gevent/libev/corecext.c:24279:36: note: each undeclared identifier is reported only once for each function it appears in
src/gevent/libev/corecext.c:24284:36: error: 'EVBACKEND_IOURING' undeclared (first use in this function); did you mean 'EVBACKEND_PORT'?
24284 | __pyx_t_1 = __Pyx_PyInt_From_int(EVBACKEND_IOURING); if (unlikely(!__pyx_t_1)) __PYX_ERR(0, 114, __pyx_L1_error)
| ^~~~~~~~~~~~~~~~~
```
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
This patchset includes a few upstream backports:
- sh: Add sh4 fpu Implies folder
- linux: Allow adjtime with NULL argument [BZ #26833]
- __vfscanf_internal: fix aliasing violation (bug 26690)
- iconv: Accept redundant shift sequences in IBM1364 [BZ #26224]
- aarch64: Add unwind information to _start (bug 26853)
- support: Provide a way to reorder responses within the DNS test server
- support: Provide a way to clear the RA bit in DNS server responses
- resolv: Handle transaction ID collisions in parallel queries (bug 26600)
- resolv: Serialize processing in resolv/tst-resolv-txnid-collision
- struct _Unwind_Exception alignment should not depend on compiler flags
- Remove __warn_memset_zero_len [BZ #25399]
- Remove __warndecl
- aarch64: Fix DT_AARCH64_VARIANT_PCS handling [BZ #26798]
Two of them are specual (noticed by Gentoo users):
- "linux: Allow adjtime with NULL argument [BZ #26833]" fixes openntpd
startup failure.
- "__vfscanf_internal: fix aliasing violation (bug 26690)" fixes gcc-11
compatibility.
Reported-by: Tobias Leupold
Bug: https://bugs.gentoo.org/756316
Bug: https://sourceware.org/PR26833
Reported-by: andy
Bug: https://bugs.gentoo.org/750992
Bug: https://sourceware.org/PR26690
Package-Manager: Portage-3.0.11, Repoman-3.0.2
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
This is neither allowed for compiled Lua modules nor, as demonstrated
by the fact simply dropping this from linker options works just fine,
actually needed in this case.
Signed-off-by: Marek Szuba <marecki@gentoo.org>
Safer that way, using two different Lua implementations at build time
and at run time can sometimes result in subtle problems that are a major
pain in the neck to debug.
Signed-off-by: Marek Szuba <marecki@gentoo.org>
Basically just incorporating the patches we already apply to prev snapshot.
Package-Manager: Portage-3.0.12, Repoman-3.0.2
Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org>
Featuring proper multi-impl support including testing. Lua bindings have
been confirmed to build, test and install fine for all five
implementations currently listed in LUA_COMPAT.
Speaking of testing, in order for it to be complete the file "test.png"
produced for each enabled Lua target by rrd.graphv should be visually
inspected. For obvious reasons automating this would be way more trouble
than it is worth (an image recogniser as a build-time dependency???),
that said I *have* inspected those images while testing whether LuaJIT
as well as PUC Lua 5.2, 5.3 and 5.4 really are supported (although
upstream documentation says "Lua 5.0 or newer" their build scripts only
explicitly mention PUC Lua 5.0 and 5.1, and LuaJIT is not mentioned in
either) and they looked fine for all five implementations.
Closes: https://bugs.gentoo.org/752780
Signed-off-by: Marek Szuba <marecki@gentoo.org>
Executing tools installed in ROOT will fail when cross-compiling,
so this prints a warning about manually running the command instead
in that case. The warning is copied from dev-libs/glib.
This also reorders the exception handling by increasing severity so
that the "nothing to do" non-error returns first, otherwise the
expected problem of unexecutable cross-compiled commands returns,
otherwise the unexpected problem of missing commands returns.
The immodule cache functions were updated to handle a different
problem. They run native tools from BROOT, but they are not
guaranteed to exist while cross-compiling (e.g. gtk+ can't BDEPEND
on itself, so the cross-compiled gtk+ can be installed before the
native gtk+, which fails from gtk-query-immodules not existing).
Closes: https://bugs.gentoo.org/611030
Closes: https://bugs.gentoo.org/757483
Signed-off-by: David Michael <fedora.dm0@gmail.com>
Signed-off-by: Matt Turner <mattst88@gentoo.org>