buildroot/package/Makefile.in, branch 2016.02

package/Makefile.in: fix typo

2016-02-01T16:19:36+00:00

Commit dc95d50fe3ee (correct gettext handling for musl) introduced a last minute typo, fix that. Thanks to Thomas Petazzoni for noticing. Signed-off-by: Peter Korsgaard

package/Makefile.in: correct gettext handling for musl

2016-02-01T16:02:06+00:00

Based on a patch by Bernd Kuhls. The AM_GNU_GETTEXT autotools macro misdetects musl gettext support as it checks for internal glibc symbols. Work around it by forcing libc gettext support when musl is used for the supported gettext api levels. As this is a generic issue for any package using AM_GNU_GETTEXT, add it to the global TARGET_CONFIGURE_ARGS instead of for each affected package. Signed-off-by: Peter Korsgaard

toolchain: granular choice for stack protector

2015-12-27T14:30:09+00:00

Currently, we only support two levels of stach-smashing protection: - entirely disabled, - protect _all_ functions with -fstack-protector-all. -fstack-protector-all tends to be far too aggressive and impacts performance too much to be worth on a real product. Add a choice that allows us to select between different levels of stack-smashing protection: - none - basic (NEW) - strong (NEW) - all The differences are documented in the GCC online documentation: https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Optimize-Options.html Signed-off-by: Steven Noonan [yann.morin.1998@free.fr: - rebase - add legacy handling - SSP-strong depends on gcc >= 4.9 - slightly simple ifeq-block in package/Makefile.in - keep the comment in the choice; add a comment shen strong is not available - drop the defaults (only keep the legacy) - update commit log ] Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni [Thomas: - only show the choice if the toolchain has SSP support - add details for the BR2_SSP_ALL option that it has a significant performance impact.] Signed-off-by: Thomas Petazzoni

Merge branch 'next'

2015-12-01T22:24:07+00:00

Signed-off-by: Peter Korsgaard

package/Makefile.in: remove HOSTCC_VERSION

2015-11-22T21:38:26+00:00

HOSTCC_VERSION is no longer used since gcc switched to the package infrastructure in e236fe481. It was in fact no longer needed since we dropped support for gcc 4.3. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard

core/pkg-infrastructures: remove LD_LIBRARY_PATH from the environment

2015-11-18T21:57:48+00:00

If system tools are selected, the host's lib/ directory may shadow libraries from the system which are configured differently and do not have all of the symbols required by the system tool. Since buildroot now uses rpath everywhere, LD_LIBRARY_PATH should not be necessary anyways. Signed-off-by: Ben Boeckel Acked-by: Arnout Vandecappelle (Essensium/Mind) Acked-by: "Yann E. MORIN" Signed-off-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

package/Makefile.in: remove BR2_TARGET_OPTIMIZATION from TARGET_CFLAGS

2015-10-28T23:02:48+00:00

Since the toolchain is always wrapped and the wrapper already passes BR2_TARGET_OPTIMIZATION (through BR_ADDITIONAL_CFLAGS), there is no longer any need to pass it in TARGET_CFLAGS as well. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Reviewed-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

xtensa: switch from text-section-literals to auto-litpools

2015-10-04T16:27:27+00:00

Now that both binutils and gcc support auto-litpools use that option instead of text-section-literals to be able to compile huge functions. Fixes: http://autobuild.buildroot.net/results/dd384fe0ef02a4205bea66a4a16ca2062afe53b4/ http://autobuild.buildroot.net/results/87dd357a4b883ea3cd75546b3d63c4c28245beee/ http://autobuild.buildroot.net/results/b5bca00dec1ecb118c7fb9c10dee74c94809c831/ and many others. Signed-off-by: Max Filippov Signed-off-by: Thomas Petazzoni

Makefile.in: remove now-unused TARGET_CC/CXX_NOCCACHE

2015-10-04T16:22:20+00:00

Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Reviewed-by: Romain Naour Signed-off-by: Peter Korsgaard

infra: move ccache handling to the toolchain wrapper

2015-10-04T16:22:20+00:00

Since we always have a toolchain wrapper now, we can move the ccache call to the toolchain wrapper. The hostcc ccache handling obviously stays. The global addition of ccache to TARGET_CC/CXX is removed, but many individual packages and infras still add it. This means we have a chain like this: ccache -> toolchain-wrapper -> ccache -> gcc However, this is fairly harmless: for cache misses, the inner ccache just adds overhead and for cache hits, the inner ccache is never called. Later patches will remove these redundant ccache calls. As a side effect, perl now supports ccache as well. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Cc: Danomi Manchego Cc: Károly Kasza Signed-off-by: Peter Korsgaard