| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
The rationale is that any exceptions to either of these checks will
probably apply to both checks. So, QA_CFLAGS_IGNORED and QA_DT_HASH
are merged into QA_FLAGS_IGNORED, and QA_STRICT_CFLAGS_IGNORED and
QA_STRICT_DT_HASH are merged into QA_STRICT_FLAGS_IGNORED.
|
|
|
|
|
|
|
| |
Current *FLAGS variables include CFLAGS, CXXFLAGS, FFLAGS, and FCFLAGS.
Not that this check is only enabled if every one of these variables
contains -frecord-gcc-switches, since otherwise the check could result
in false positive results.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This adjusts the logic from commit
ff52f9dc31004becb8022e6437088d01917f413c to use FEATURES=force-prefix
instead of USE=prefix. This has the advantage that we don't have to
make any assumptions about the USE=prefix.
|
|
|
|
|
|
|
|
| |
This is safe because the prefix flag should be masked in all non-prefix
profiles, and older EAPIs would otherwise be useless with prefix
configurations. This brings compatibility with the prefix branch of
portage, which also supports EPREFIX for all EAPIs (for obvious
reasons).
|
|
|
|
|
|
|
| |
The EPREFIX variable is not readonly in EAPI 0, 1, and 2, so we can
declare EPREFIX as a local variable. We must be careful not to let this
variable leak into the environment of ebuild/eclass functions that we
call, since bash propagates local variables to nested function calls.
|
|
|
|
|
|
|
| |
The ED variable is not readonly in EAPI 0, 1, and 2, so we can declare
ED as a local variable. We must be careful not to let this variable
leak into the environment of ebuild/eclass functions that we call,
since bash propagates local variables to nested function calls.
|
|
|
|
| |
This allows our prefix tests to use helpers like insinto, doins, and dosym.
|
| |
|
| |
|
|
|
|
|
|
| |
Having sleep in the world-writable loop causes riduculous delays for
prefix users with exotic filesystem constraints (like a FAT filesystem
mounted with umask=000).
|
| |
|
|
|
|
|
| |
in addition, omit the leading slash, since PORTAGE_CONFIGROOT contains a
trailing slash
|
| |
|
| |
|
|
|
|
|
| |
Refer to "severe warnings" rather than "poor programming", in order to
be more politically correct, as discussed in bug #374233.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When ROOT != /, binaries that reference ROOT will load their
dependencies from ROOT first rather than from the system-configured
path. This is a problem because the ROOT will be / on the target
system.
Besides the above, this patch also fixes incorrect parsing of scanelf
output, where we would treat the RPATHs returned by scanelf as the
names of binaries.
TEST=When "stricter" FEATURE is enabled, verify that emerge
fails when an ebuild references broken rpaths referencing
ROOT. When "stricter" FEATURE is not enabled, verify that such
references are automatically fixed. Also verify that ebuilds
with non-broken RPATHs (e.g. RPATHs referencing $ORIGIN/../lib)
are not touched by the change.
BUG=chromium-os:14271
Change-Id: I4f29cc4ea9195a1255f080284da1f676e4a2c26b
Review URL: http://codereview.chromium.org/6903153
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Moving these commands from shell to Python helps avoid an unnecessary
call to misc-functions.sh for the postinst_bsdflags. This improves
performance.
BUG=none
TEST=Run emerge-x86-generic -eg --jobs=16 libchrome
Change-Id: I0c2af50b4d2f7644cabac84fde7fe4d682010c69
Review URL: http://codereview.chromium.org/6676107
|
| |
|
| |
|
| |
|
|
|
|
| |
This solves cases like bug #350045.
|
|
|
|
|
| |
It should be faster to use the bash builtin, and also allows us to
avoid issues with touch breakage (like in bug #348640).
|
|
|
|
| |
This should fix bug 342721.
|
|
|
|
| |
ebuild(1) calls the 'package' phase.
|
|
|
|
| |
in LDFLAGS, in order to try and filter out invalid settings.
|
|
|
|
| |
warnings fatal for now.
|
|
|
|
|
|
| |
these deprecated directories:
etc/app-defaults usr/man usr/info usr/X11R6 usr/doc usr/locale
|
|
|
|
| |
intended for "implicit pointer".
|
|
|
|
|
| |
from the "implicit pointer" code in install_qa_check(), so they
don't interfere.
|
|
|
|
|
| |
gcc warning fatal. Thanks to Diego Pettenò <flameeyes@g.o> for the
suggestion.
|
| |
|
|
|
|
|
|
| |
first check for non-empty $SANDBOX_LOG and signal unsuccessful exit
if necessary. This fixes an issue with phases being treated as
successful even when there were sandbox violations.
|
|
|
|
|
|
| |
PORTAGE_BUNZIP2_COMMAND settings in make.conf. This only adds support
for binary packages, since that's where pbzip2 can provide the most
benefit in common cases.
|
| |
|
|
|
|
|
| |
Expand symlinks in prepcompress() completely, not only to the last
directory component.
|
| |
|
| |
|
|
|
|
|
| |
about these policy decisions being included in portage. Besides, these
kinds of things could go in the python eclass.
|
|
|
|
|
|
|
| |
all build logs to be compressed while they are being written. Log file
names have an extension that is appropriate for the compression type.
Currently, only gzip(1) compression is supported, so build logs will
have a '.gz' extension when this feature is enabled.
|
|
|
|
|
| |
intermittent build failures in my stage builds. For testing purposes
set PORTAGE_IPC_DAEMON_ENABLE=1 to enable EbuildIpcDaemon.
|