| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Bug: https://bugs.gentoo.org/588198
|
|
|
|
| |
Gentoo-bug: 587998
|
|
|
|
|
|
|
|
| |
This used to "work" because gcc-version relied on gcc-config, even if GCC was
not the active compiler. gcc-version has since been fixed to always use CC
instead.
Gentoo-bug: 587998
|
|
|
|
|
|
|
|
|
| |
HOST_CC and HOST_CXX are used to build tools like nsinstall which are needed
to install later on. Until now, these values were undefined and for whatever
reason were never autodetected to match the CHOST based tools. This commit
should resolve that issue.
Bug: http://bugs.gentoo.org/565124
|
|
|
|
|
|
| |
Bug: http://bugs.gentoo.org/587334
Package-Manager: portage-2.2.28
|
|
|
|
|
|
|
|
|
|
| |
mozconfig
mozilla-48 and newer have dropped some configuration options that are no longer used
in the build system, and due to the way the new python configure operates, any options
specified that are not recognized are fatal. Moving these options out of mozcoreconf
allows the older mozconfig's to retain the same configuration while also allowing newer
mozconfig's to drop them as appropriate.
|
| |
|
|
|
|
|
|
| |
1) 15.08.x has left the tree
2) Prepare for a future kde4-l10n without USE=minimal
Version block makes sure of no ancient kde4-l10n anyway
|
|
|
|
| |
is defined
|
|
|
|
|
| |
KDE_GCC_MINIMAL will now only be exported in packages that require it, as it
triggers an expensive pkg_pretend check whenever it is defined.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Exporting pkg_pretend is expensive, even if the exported function is a noop.
As kde5_pkg_pretend is currently only used to check if the active GCC version
is recent enough, only export that phase if it will have something to do.
The number of situations in which KDE_GCC_MINIMAL is exported will be
substantially reduced in a future commit. This will result in a large time
saving at the beginning of the emerge process as we will no longer see hundreds
of lines of:
>>> Running pre-merge checks for kde-foo/bar-123
>>> Running pre-merge checks for kde-foo/baz-123
|
|
|
|
|
|
|
|
| |
This avoids bugs where too many arguments are passed by mistake, causing the
last one to be ignored.
For example, the subslot operator added in d1bc5ac3f0e42df0f0255c8b39d7df16c5d4176b
was never applied because too many '' were passed.
|
| |
|
|
|
|
|
| |
Newer versions offer a configure flag so we don't have to manually patch
in the default setting.
|
|
|
|
| |
Bug: https://bugs.gentoo.org/577704
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Anthony G. Basile <blueness@gentoo.org>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Also move to sys-fabric category
|
|
|
|
|
|
|
| |
Base eclass for cargo that handles setting up the cargo registry and
provides a way to fetch crates.
Signed-off-by: Doug Goldstein <cardoe@gentoo.org>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
After commit 81c226e451be564a545696f93fc5880ebc160812, type cannot be
"kern" in these two places, so ninj would always return its second
argument, i.e. it can be replaced by simple echo.
|
| |
|
|
|
|
|
|
|
|
| |
Remove the support for old kernel versions that are no longer used
in Gentoo, and rely on KV_to_int() function. This functions is provided
by Portage but not listed in PMS. Furthermore, for a long time Portage
replaced it with 'return 1' in global scope, so they did not really work
as expected anyway.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Add a tc-get-compiler-type() function that can be used to identify
the compiler being used, using the preprocessor defines. Alike
gcc-*version() routines, it uses CPP (which in turn uses CC).
The major usage would be applying compiler-specific quirks and limiting
gcc version checks to compilers that actually are gcc, since e.g. clang
reports gcc version 4.2 -- which would incorrectly cause numerous gcc
version checks in ebuilds to fail.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Modify the tc-getCPP and tc-getBUILD_CPP functions to use "$(tc-getCC)
-E" (i.e. the C compiler's preprocessing call) instead of falling back
to 'cpp'. This ensures that in environment with CC (and CXX) overriden
the correct compiler is used rather than the one selected by gcc-config,
which in turn fixes gcc version queries.
The alternative would be to always override CPP along with CC & CXX.
However, that is uncommon and is known to break some packages.
Bug: https://bugs.gentoo.org/show_bug.cgi?id=582822
|
|
|
|
|
|
| |
Fix _tc-getPROG function to account correctly for default values that
contain program name along with arguments, e.g. the default for CPP
containing "$(CC) -E".
|
|
|
|
|
|
| |
See virtual/gnat changes and ebuild updates.
Signed-off-by: Stephen L Arnold <nerdboy@gentoo.org>
|
| |
|
|
|
|
|
|
|
| |
qtdeclarative was revbumped due to the inclusion of an important patch. All
other modules had either trivial or no changes.
Gentoo-bug: 586646
|
| |
|
|
|
|
|
|
|
|
| |
The USE=multislot was used only to control build-time blocker on
previous versions of binutils. However, there is no technical reason not
to have multiple binutils versions installed at build time (or run
time). Considering that the flag does not control the installed files or
the package in any other way, it is an invalid use of USE flags.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The USE=multislot as defined partially by toolchain.eclass and partially
by sys-devel/gcc was used for two purposes:
- enabling build-time (only) blockers on old gcc versions -- which do
not make any sense because they are build-time only and there is no
technical reason for two gcc version ranges not to be installed at
the same time, both at build time and at run time,
- changing behavior of post-install wrt conditional gcc-config calls.
Both cases are invalid use of USE flags, considering that the flag does
not affect the installed files in any way.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
kgenapidox was removed from kapidox in bb4063f5d9f9015b86dbc3a48a424c8cb1a8193f
and there does not appear to be a suitable replacement (for us).
|
|
|
|
| |
KDE_DESIGNERPLUGIN toggles dependencies and configure with USE=designer
|
| |
|
| |
|
|
|
|
|
| |
The variable holding the min version requirement can be named anything.
This should catch most cases, most importantly Qt5 modules.
|
|
|
|
|
| |
This mirrors the behaviour during src_configure where cmake and its arguments
are printed for clarity.
|