Add TARGET_GCC_VERSION

Default to 4.6, but can overwritten to something else in
prebuilts/gcc/$os/$arch/$arch-linux-android*-$ver

Change-Id: I16f99d642b8ff8e831d392261a0c536041107051
[ARM] Extend the usage of TARGET_GCC_VERSION for gdb and arm-eabi-*.

In the future to upgrade the gcc version we just need to edit one
line in core/config.mk.

Change-Id: I01bb38c38f2388913bb7369aa4b2da480411dfbe
Export TARGET_GCC_VERSION as an env variable.

Have it referenced by the adbs tool to pick the specified toolchain.

Change-Id: I23df88946254a55d0749d6753e54559faf33e121
x86: enable FORTIFY_SOURCE

Enable FORTIFY_SOURCE for Android x86.  This adds certain security
protections to Android programs, checking for common programming
mistakes and buffer overflows.

FORTIFY_SOURCE protections have been enabled for ARM since
a46c480e43cc61d0190569684f0a1e53a5da75b6 (Jun 4th 2012)

Change-Id: Idae6f93d37ddae605088867cd3029f12632456e1
Use GCC 4.7 from google

Thanks aaronpoweruser for saving me hours of fixing errors myself.

Change-Id: I85cdd49a802bc9577e40bccbcfa2b08f3c76a472
Signed-off-by: Stevespear426 <stephen.k.spear@gmail.com>
GCC 4.7 O3 and aliasing Optimizations

Requires http://gerrit.sudoservers.com/#/c/4568/ to build.

Change-Id: Ic416df6a593d1094deaac5a2261b625f734ce404
Add strict_aliasing.
build/core: Build in ISOC++11 mode if possible

Add -std=gnu++11 if the compiler supports it

Change-Id: Ied8b4487263172b678fd2912cfe428187b2edf95
Signed-off-by: Bernhard Rosenkraenzer <Bernhard.Rosenkranzer@linaro.org>
envsetup: set OUT_DIR to an absolute path always

OUT_DIR was set to $(TOPDIR)out previously,
but $(TOPDIR) was null, so it was a relative path.
This broke releasetools, inline kernel building, etc
since they require absolute paths.
Fix it so that it is set to $(shell readlink -f .)/out
if $(TOPDIR) is null.

Also remove hacks which checked if (OUT_DIR) was out
and changed it to $(ANDROID_BUILD_TOP)/out to workaround
the aforementioned problem.

Change-Id: I459a3b1325a1bbea0565cd73f6acf160d4ed9b39

Conflicts:
	core/envsetup.mk
build: Don't build the recovery-from-boot patch on CM

 * We don't use this, and I am running into a weird bug where imgdiff is
   hanging on a specific target. Just disable it for now.

Change-Id: I25ee666136e25994528eaa32b6f787626cd288ed
This is rootbox son
Remove the line that deletes *.rc from the recovery ramdisk.
This is no longer necessary since recovery init.rc only includes "import /init.recovery.${ro.hardware}.rc".

Fix up the unpackbootimg target.

Change-Id: I30b515bda982fbd944fffbc64501588cd3702dd8

Conflicts:
	core/Makefile