| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Replaces the deprecated MATURIN_PEP517_ARGS and will also
allow ebuilds to enable/disable cargo --features through
DISTUTILS_ARGS like the rest should the need arise.
Support was technically added in 0.15.3, but 1.0.0 allows
passing an array rather than only a to-be-shlex.split string.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Closes: https://github.com/gentoo/gentoo/pull/31143
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
|
|
|
| |
Starting with Python 3.12, the standard unittest runner exits
unsucessfully if no tests are found. Therefore, we no longer need
to use unittest_or_fail.
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
|
|
|
| |
This gives a nice speedup to net-fs/samba, which (re)links several
hundred files in its install phase.
Bug: https://bugs.gentoo.org/715542
Signed-off-by: Mike Gilbert <floppym@gentoo.org>
|
|
|
|
| |
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Unfortunately, we have to use -j1 for make install. Upstream
don't really test it and there's not much appetite for fixing bugs
with it. Several reported bugs exist where the resulting image
was wrong, rather than a simple compile/install failure:
This reverts commit db0387530cf744068f480b68a192d4fc10a81286.
Closes: https://bugs.gentoo.org/906155
Bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42980
Bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51814
Bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103656
Bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109898
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
| |
Thanks to Ionen for reporting.
Fixes: 3bce8799e4791f9d2fcb94e5c1ae287632ad7286
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
| |
Do not require a separate manpage dist for every minor release.
Instead, use the 16.0.4 tarball for 16.x releases going forward.
This makes sense since manpages rarely change -- at least for all
the 16.x releases, all that's been changing were the build date
and the version number in extraclangtools manpage.
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
|
|
|
|
|
| |
When the kernel configuration contains the setting
CONFIG_MODULE_COMPRESS_{GZIP,XZ,STD} we need to store
the extension for a subsequent call to modinfo.
Closes: https://bugs.gentoo.org/906303
Signed-off-by: Mike Pagano <mpagano@gentoo.org>
|
|
|
|
|
|
|
| |
This reverts commit 7a0a0ebb526cce917c052f540037ba0519a20c42.
Bug: https://bugs.gentoo.org/905901
Signed-off-by: Matt Turner <mattst88@gentoo.org>
|
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/906385
Closes: https://bugs.gentoo.org/906376
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
|
|
| |
Thanks to robbat2 for providing feedback.
Closes: https://github.com/gentoo/gentoo/pull/30603
Signed-off-by: Florian Schmaus <flow@gentoo.org>
|
|
|
|
| |
Signed-off-by: Hans de Graaff <graaff@gentoo.org>
|
|
|
|
| |
Signed-off-by: Hans de Graaff <graaff@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/885099
Closes: https://bugs.gentoo.org/903746
Closes: https://github.com/gentoo/gentoo/pull/28634
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
| |
as @INCLUDES_EPREFIX"
This reverts commit 8e995bcf32d50c7eae950eb42d84e37d31b0d76b.
This confuses pkgcheck and eclass-manpages too much.
Bug: https://github.com/pkgcore/pkgcore/issues/404
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
| |
It errors out otherwise with "no description".
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/905901
Closes: https://github.com/gentoo/gentoo/pull/30923
Signed-off-by: Matt Turner <mattst88@gentoo.org>
|
|
|
|
| |
Signed-off-by: Ulrich Müller <ulm@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
| |
The CONF_LIBDIR variable was used exclusively in the 2004.3 profile
(i.e. it was no longer defined in 2005.0), before the ABI and
LIBDIR_${ABI} variables existed.
Simply use "lib" as default, which is consistent with get_libdir().
Bug: https://bugs.gentoo.org/267159
Signed-off-by: Ulrich Müller <ulm@gentoo.org>
|
|
|
|
| |
Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org>
|
|
|
|
|
|
|
| |
Followup to e6dd349ea37663f3e3a6ce1df3fd9f7cf18e20cd.
Closes: https://bugs.gentoo.org/906007
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These don't seem to be necessary at all now:
- we don't sed info pages anymore because GCC has support for setting
the bug URL + distributor now
- there's info pages in other directories than gcc/ (e.g. libgccjit)
With 12.3.0, I had without this:
```
* CMP: =sys-devel/gcc-12.2.1_p20230505 with sys-devel/gcc-12.3.0/image
* FILES:-usr/share/gcc-data/x86_64-pc-linux-gnu/12/info/gfortran.info
* FILES:-usr/share/gcc-data/x86_64-pc-linux-gnu/12/info/libgccjit.info
* ------> FILES(-2) ABI(TIMEOUT)
```
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/215828
Bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35855
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
| |
Ionen rightly points out that people might have -flto by default and
-fno-lto in package.env.
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
| |
We already allow -Os and -Oz is just a more aggressive version of that.
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
| |
LTO is pretty safe nowadays and packages broken with it should really use
filter-lto specifically instead.
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
whitelist)
-fstack-check is _not_ a safe flag:
* https://developers.redhat.com/blog/2017/09/25/stack-clash-mitigation-gcc-background
* https://developers.redhat.com/blog/2019/04/30/stack-clash-mitigation-in-gcc-why-fstack-check-is-not-the-answer
Nobody is really interested in maintaining this functionality upstream in GCC
anymore for this reason, it's not IIRC supported in Clang, and we're not testing
it either.
Please use the far superior -fstack-clash-protection instead.
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
| |
-O3 is perfectly safe in the absence of UB. And with UB, -O2 and friends can
easily break with new compiler versions and such anyway.
In addition, I'd say that -O/-O1 is probably as risky as -O3 nowadays, if not
more, because if nothing else, you don't get a bunch of hardening.
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
|
|
| |
Fix DISTUTILS_EXT to add IUSE=debug even if DISTUTILS_OPTIONAL is used.
This was the intended behavior, as documented in the Python Guide.
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When not passing an explicit build directory, meson-python configures
meson into a build directory that is rooted in a tempdir with a random
suffix. This results in unstable paths, which currently disappear after
meson-python completes (either with success or failure). It doesn't
handle incremental or resumed builds, and it's very difficult to debug
-- for example by inspecting the logfile that meson itself prints out
when the configure stage fails.
Bug: https://bugs.gentoo.org/905396
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
| |
Signed-off-by: Michał Górny <mgorny@gentoo.org>
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
ebuilds
Without this, gcc --version ends up only showing the commit resulting from
applying our patches on top.
With this fixed, gcc --version shows both the upstream commit & the commit hash
after applying patches.
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
|
| |
This should be set in profiles going forward, not in toolchain.eclass.
Bug: https://bugs.gentoo.org/890999
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
|
| |
@INCLUDES_EPREFIX
Signed-off-by: Sam James <sam@gentoo.org>
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/904677
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
|
|
|
|
| |
We dropped them to ~arch a while ago.
Signed-off-by: Sam James <sam@gentoo.org>
|