| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
| |
This reverts commit cc95d2b6c234982b6b54a0b82e0ca5c5c1361f57.
Change-Id: I40fa79992814f1a24174137f7b95a1e19a86828d
Link: https://android.googlesource.com/kernel/msm/+/0a659ab3a797c3311d0f697e9b443054ace9a4aa
Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The GCC wrapper writes any error message from GCC to stdout
along with the messages from the wrapper itself. This is okay
for most case, but when GCC is used with -print-xxx flags,
the stdout output is supposed to be taken as input to some
other build command, so putting error messages in there is
pretty bad. Fix this by writing error messages to stderr.
Change-Id: I4656033f11ba5212fdcc884cc588f8b9d2c23419
Signed-off-by: Shadab Naseem <snaseem@codeaurora.org>
|
| |
|
|
|
|
| |
Bypass a few forbidden warnings to allow msm_defconfig to build.
Signed-off-by: David Keitel <dkeitel@codeaurora.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Many systems these days have both python2 and python3 installed. The
unversioned executable `python` may point to either version. Per
https://www.python.org/dev/peps/pep-0394/ , scripts that need Python 2
should explicitly call this out in the shebang line.
These build scripts are both specific to python 2, so call this out in
the shebang line.
Change-Id: I11f70c341e484254dc1679db65c2ed5ac61e510f
Signed-off-by: David Brown <davidb@codeaurora.org>
|
| |
|
|
|
|
|
|
|
|
|
| |
Bypass forbidden warnings in code coming from upstream in order to
avoid compilation errors with gcc5.
sysrq.c:956:33: warning: array subscript is above array bounds
hci_sock.c:980:8: warning: passing argument 2 of 'hci_test_bit'
discards 'const' qualifier from pointer target type
Change-Id: I5056078112fdc457c424c0f49c4dca70c6b97c29
Signed-off-by: Se Wang (Patrick) Oh <sewango@codeaurora.org>
|
| |
|
|
|
|
|
|
| |
Bypass forbidden warnings in code coming from upstream in order to
avoid compilation errors for msm-3.18 and remove bypassed warnings
from msm-3.14.
Signed-off-by: Ian Maund <imaund@codeaurora.org>
|
|
|
Rather than telling gcc to make warnings as errors, and then hunting
down make rules to disable this, leave them as warnings, but invoke
gcc through a wrapper that checks the warnings against a whitelist.
The initial whitelist comes from the warnings in the current build,
all of which have been allowed through Make overrides.
Change-Id: I5e0b199f9803d072537eeb77cb38d91cc06e951b
Signed-off-by: David Brown <davidb@codeaurora.org>
[mattw@codeaurora.org: update allowed_warnings for msm-3.14]
Signed-off-by: Matt Wagantall <mattw@codeaurora.org>
|
