| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The kernel security team asked us to fix this bug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46639
This CL does that.
Note: This CL depends on
https://android-review.googlesource.com/329799
Bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46639
Test: Ran build.py for all toolchain versions; used resulting
compilers to build bullhead, angler and fugu plaform images.
Ran checkbuild.py.
Change-Id: I1e1abf594cff56c6ed6dc228a1d084da18c11420
|
|
|
|
|
|
|
|
|
|
|
|
| |
Disabling multilibs fixes the GCC builds for both MIPS and
x86_64. Without this, the GCC compiler fails to build for those
architectures.
Bug: None
Test: Ran build.py without '--toolchain' flag; it successfully built
all of the compilers.
Change-Id: I018825177e77812a705db54cdad468239e48a87f
|
|
|
|
|
|
|
|
|
|
|
|
| |
This add a python wrapper for gcc to make goma do not need to
hand gcc and clang separately.
BUG 31444867
TEST= build new gcc. Call arm-linux-androideabi-c++ -v
and arm-linux-androideabi-g++ -v in/out the directory of
the gcc binary, it works.
Change-Id: Ib02cff8f33306b089e13ade51033a3b0927b4308
|
|
|
|
|
|
|
|
|
|
| |
This CL adds a top-level configure flag, --enable-libatomic-ifuncs.
IF this is set to 'no', then libatomic will not be configured/built
to use IFUNC.
This is to fix https://buganizer.corp.google.com/issues/22699878
Change-Id: I76741fe854fc9c32a230b67c72920adfb00473ee
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This CL updates Android's GCC to match ChromeOS's GCC (with
appropriate patches applied in both places to make sure no
cherry-picked changes are lost).
Change-Id: I390140c449b0e5df9ee78a06268319c8c510302f
|
|/
|
|
|
|
|
|
|
| |
The Windows (and probably Darwin) builds were missing the lib64
variants of libgomp.a and friends. This will still miss the libx32
libs, but we don't support that anyway.
Bug: http://b/27208805
Change-Id: I19a8eb10cbedf03cba27ab5f8dc38c13c8538f25
|
|
|
|
|
| |
Bug: http://b/22045105
Change-Id: I3ac05c6bfe9875583a15383dc5840b3f8a37e22d
|
|
|
|
| |
Change-Id: Ie2afa1b7cabea7a681116822ddd888bdb297dbae
|
|
|
|
|
|
|
|
| |
Override CXXFLAGS when building for debugging (so
as to insure that C++ code is compiled correctly
as well as C code).
Change-Id: I70e285be236b33f07594aef2adbf2fbd73b4a909
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The toolchains built here are used for the platform too. Remove the
NDK path structure from the package. We can handle that in the NDK
build.
Change-Id: I108154a6b9726cd3757b9ad548ef2d95be1ecf9b
|
|/
|
|
|
|
|
| |
I had previously added all these to the prebuilts directories by hand.
Doing it at this stage ensures that we'll always have them.
Change-Id: Iaebed3990bff79730073202e808c5d47cb55326f
|
|
|
|
|
| |
Bug: http://b/24990121
Change-Id: Id6f6596c5277279e02dce4f3f44356bc4a865765
|
|
|
|
|
|
|
|
|
|
| |
Create a link in /tmp to the prebuilt sysroot and
pass the link location to the gcc configure script;
this is intended to avoid hard-coding buildbot
pathnames into the gcc binary.
Bug: 25513824
Change-Id: I49dddde6f91a9737a8b8a27802acfc7133dd63af
|
|
|
|
| |
Change-Id: I7efa94dc03c6a2b15fda6c84f3480ac4674205c0
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Add an option to build-gcc.sh to build a more
debuggable (-O0 -g, not stripped) copy of gcc.
Change-Id: Ieabcfc8b02796041eb89fa4c1b9614994466a5b6
|
|/
|
|
| |
Change-Id: If59bf26456eeb476d9f6e641a6aad0e433112546
|
|
|
|
|
|
|
|
|
|
| |
Fix some issues that crop up when using build-gcc.sh on post-4.9
versions of GCC (for triage/bug-reproduction purposes): trunk gcc
calls isl directly, no longer through "cloog", and requires updated
version of ISL. Resulting build still fails compiling libatomic,
however the cross compiler itself is still usable.
Change-Id: I8caa936172a4b2093938bda44a452aa4d841df8d
|
|
|
|
|
|
|
|
| |
We don't need to be archiving these build artifacts in their extracted
form on the build server. Build and install to $TMPDIR, but still
package that tarball into $PACKAGE_DIR.
Change-Id: Iba42c19e0f7b49f2da608b577579fcc8871eb85c
|
|
|
|
|
|
|
| |
This used to be handled by package-release.sh, but we now need to
perform the full build/package step here rather than in ndk/.
Change-Id: Ia8a1662fd5c6adec72f83d15374af6f4bfa04afd
|
|
|
|
| |
Change-Id: Iff7e294f5bf08048d019f39465d377cfb9782866
|
|
|
|
|
|
|
| |
This is unused and we already get this from libgcc.
Change-Id: I1b1a405662294a3395928bc42e395271f758c40a
(cherry picked from commit c622d534cf0921bd22c4afe5060520f8fdd49d08)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Apparently we've been packing an empty tarball of the toolchain since
I split up the toolchain build because the script defines the install
path in a few different places.
Fix the toolchain install path to match the format we expect
(toolchains/$HOST/$TOOLCHAIN/prebuilt), improve logging, and actually
fail the build if we can't package the toolchain.
Change-Id: I093ca747af13b5ed093cb43499ea1fdb9aed0430
(cherry picked from commit dd4155a395690bbe0372cf9ec63dd2ed85e7b81c)
|
|
|
|
|
|
|
|
|
|
| |
We're building against an old version of libc to check this already,
and the script doesn't seem to be checking the right things anyway (we
don't support older than 2.11). To top it all off, we haven't been
checking this for failure anyway.
Change-Id: I67e6b03cf7c3cce66cfb4c69dd18d8b9a6f31806
(cherry picked from commit 13185e44b81bb04268394f30efa7b0649c43e8ce)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using the build scripts from prebuilts/ndk makes the edit/compile
cycle complicated since we have to either edit in ndk/ and copy to
prebuilts/ or vice versa.
The prebuilt NDK build scripts should really just be whatever build
scripts we end up shipping with the modular NDK (i.e. anything that
supports ndk-build or the tests rather than things used to build the
NDK itself).
Change-Id: Id995397d6272f1539037a19287cc8a69fdb4b8a1
(cherry picked from commit 79ee432e58c7b1a4ae92aa2886ecd96173acbdf6)
|
|
|
|
|
|
|
|
|
|
|
|
| |
We should be doing this for the others, but there are still some build
issues to work out.
Note that this change was made to ndk/, but that was done after I had
copied build-gcc.sh here and I mistakenly forgot to apply it here as
well.
Change-Id: I2289c9d4da41eee8ce1d75324ccabf30adb7bd01
(cherry picked from commit da6ed85636572e47535ffd4fe6ab4790921c6508)
|
|
|
|
|
|
|
|
|
| |
We don't seem to need this. It was only used when configuring gcc, and
that isn't necessary. This is probably here as a relic from when we
used to build the gdb stub in this file.
Change-Id: Ieaa2f3c0200b9f569842caec2157f98d3e1a9c64
(cherry picked from commit 7ab70b0aa76254c36bdbf071e2463409115ab875)
|
|
|
|
|
|
|
|
| |
We have an out directory. Install GCC there rather than to $NDK (by
any of its many names).
Change-Id: I772ffc9230d3b1123a3cc25ebd9adc01e354c17f
(cherry picked from commit 7f738ff0092916749c3cde03c9403e3467eb0d13)
|
|
First, the platform toolchains building with the NDK build scripts
was odd.
Second, this moves us toward a more modular NDK. The path forward is
building GCC separately, installing it to prebuilts/ndk, and then
using it directly from there when building other NDK components.
Bug: http://b/23362228
Change-Id: I21448e470b4c3353bd49a1fec7d187a8376f3d82
(cherry picked from commit 51f25cab1eccd079214b9e08f5fe1bbe9368e1b0)
|