| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
Simply inline the 2 (two!) header lines instead.
Bug: 416739
|
| |
|
| |
|
|
|
|
| |
global scope. Closes bug 629106.
|
|
|
|
| |
All EAPI0 gnustep ebuilds were updated or dropped
|
|
|
|
| |
Bug: http://bugs.gentoo.org/591438
|
|
|
|
| |
variable
|
| |
|
|
|
|
|
|
|
| |
-freorder-blocks is enabled by default on -O and upper.
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
Signed-off-by: Matthias Maier <tamiko@gentoo.org>
|
| |
|
|
|
|
|
|
|
|
| |
Include LDFLAGS in the variables stripped by strip-unsupported-flags.
The code reuses the current functions for testing CC, and so only remove
LDFLAGS that are rejected by the C compiler and not the linker. This
solves the case of bug #621274 where LDFLAGS contained GCC-specific
-flto flag.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
By default, clang considers unused arguments as error when -Werror is
used. Since flag tests are performed without linking, this causes all
tests for linker flags to fail inadvertently and all those flags
are stripped as a result.
While the correctness of passing unused flags is doubtful, silently
stripping them in a few random packages is certainly not the solution
to the problem, and also makes the results differ between gcc and clang.
To account for that, use clang's -Qunused-arguments option to silence
unused argument warnings.
To avoid wasting time on testing the compiler, just try passing
-Qunused-arguments every time a flag check fails. If clang is not used,
the additional call will fail just the same as the previous one (either
because of the original flag or because of -Qunused-arguments), so
the result will be the same.
|
| |
|
|
|
|
|
|
|
| |
Explicitly warn about any URI that uses an unsecure protocol (git, http)
even if it's a fallback URI. This is necessary because an attacker may
block HTTPS connections, effectively forcing the fallback to
the unsecure protocol.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Gentoo-bug: 620766
Closes: #5470
|
|
|
|
|
|
| |
We need to wait until removal of the package.
This reverts commit edca947c05c8f83ab1bfd776bf3ea5e629609972.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Searches for test subdirectory pattern in CMakeLists.txt recursively,
enclose it with BUILD_TESTING conditional.
Creates unified diff to easily pick up for cosmetics and submission
upstream.
Re-order unconditional Frameworks tests disabling to produce more
compatible forceoptional-recursive tests.
|
|
|
|
| |
Raise PLASMA_MINIMAL to 5.10.4.
|
|
|
|
| |
This makes dev-qt/qtsql:4 and dev-qt/qt3support:4 optional.
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.3
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Introduce the support for llvm_check_deps() function to override
the default LLVM slot acceptance test (checking whether sys-devel/llvm
is installed). This can be used to match more complex dependency
specifications, e.g. to find a LLVM slot that has a matching clang
version, or to request USE dependencies on LLVM or clang.
|
|
|
|
|
|
|
|
|
| |
Ensure that a specific LLVM slot is installed via using has_version on
"sys-devel/llvm:${SLOT}" rather than checking whether llvm-config is
installed in expected location. While it is a bit slower, this is closer
to a canonical way of testing it and will be useful when we allow
testing for more specific dependency strings. Right now, it could be
helpful if one has broken LLVM installation (i.e. stray files).
|
|
|
|
| |
This eclass has always been unaware of KDE_BLOCK_SLOT4.
|
|
|
|
| |
This reverts commit 92c7fa972f87370dea450132ac6629dc7d514871.
|
|
|
|
|
| |
See also:
https://mail.kde.org/pipermail/release-team/2017-August/010526.html
|
|
|
|
| |
No ebuilds of this type should exist at this point after pkgmoves done.
|
| |
|
| |
|
| |
|
|
|
|
| |
This eclass has always been unaware of KDE_BLOCK_SLOT4.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The --enable-maintainer-mode flag serves two purposes: first, it
enables compile-time warnings; and second, it forces all compiled
modules to be loaded at runtime. To achieve the first goal, the build
system checks for the "-std=c89" compiler flag and appends it to
CFLAGS if found. This can cause a problem later, because the CFLAGS
used to build apache are used by apxs to build extension modules.
In particular, if you have an extension that relies on C99 or some
later standard, and if apache was built with --enable-maintainer-mode,
then apxs will attempt to build that extension according to C89 and
fail. This failure can be observed in in bugs 621686, 621756, and
621794 when apache is built with USE=debug, because USE=debug sets
the --enable-maintainer-mode flag.
Since there is not much reason for an end user to enable maintainer-
mode, the simplest fix for this is the wholesale removal of the
--enable-maintainer-mode flag from USE=debug. This prevents us from
having to append CFLAGS to each extension package that uses a later
standard, or from having to add a USE dependency forbidding USE=debug
in apache (which would create conflicts with e.g. mod_backtrace).
Gentoo-Bug: 621686
Gentoo-Bug: 621756
Gentoo-Bug: 621794
|
|
|
|
|
|
|
| |
The current logic strips too much, causing build failures. Revert it
until we get it right.
Bug: https://bugs.gentoo.org/627474
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/4467
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-ggdb3 builds debug information for macros into binaries. For this reason,
the C preprocessor includes all #defines as-is in the output. The check
in tc-enables-* expects only a fixed output of "true", which fails in this
scenario.
To fix this, `grep` is used to look specifically for "true" in the output
from the preprocessor.
Closes: https://github.com/gentoo/gentoo/pull/5359
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
Signed-off-by: Matthias Maier <tamiko@gentoo.org>
|
|
|
|
|
|
|
|
| |
Include LDFLAGS in the variables stripped by strip-unsupported-flags.
The code reuses the current functions for testing CC, and so only remove
LDFLAGS that are rejected by the C compiler and not the linker. This
solves the case of bug #621274 where LDFLAGS contained GCC-specific
-flto flag.
|