buildroot/package/Makefile.in, branch 2016.08

Revert "package/Makefile.in should grab HOST_DIR headers using -isystem instead of -I."

2016-07-30T16:10:18+00:00

This reverts commit 6f8162cf8c1abef7e0a4771fe0d6b26a28f5c2b6. This is causing too many problems that are not easy to solve. Signed-off-by: Thomas Petazzoni

package/Makefile.in should grab HOST_DIR headers using -isystem instead of -I.

2016-07-25T21:46:19+00:00

HOST_CFLAGS includes a search path for HOST_DIR/usr/include using -I. When HOST_CFLAGS is used by a package, these flags are passed to the compiler ahead of flags passed by the package's internal make system. If a package has a header file with the same name as a header file in HOST_DIR, this causes the toolchain to prefer the file from the system include directory because its -I appears first on the command line. Conflicts should prefer the file provided by the package. This can be accomplished by using -isystem, which is more appropriate then -I for system-level include paths. Real-world example: libfdt might be installed in HOST_DIR to install a patched version of QEMU that does not bundle libfdt. Meanwhile, the u-boot package provides its own copy of libfdt.h that is modified from upstream. If libfdt is also installed into HOST_DIR, then host-uboot-tools fails to build because it grabs the libfdt.h from the HOST_DIR area instead of using the patched version from its own source tree. This patch corrects this issue. This assumes the -isystem flag is supported by the host compiler, which is the case since gcc 3.0 at least. Signed-off-by: David Raeman Signed-off-by: Thomas Petazzoni

package/Makefile.in: set variables for legacy f77 checks

2016-07-01T21:01:25+00:00

For fortran detection, some projects check for fortran availability using the FC/FCFLAGS variables, and others for the legacy F77/FFLAGS ones. So, make sure the legacy fortran F77 and FFLAGS variables are set in TARGET_CONFIGURE_OPTS. Signed-off-by: Samuel Martin Signed-off-by: Thomas Petazzoni

package/Makefile.in: set TARGET_FCFLAGS variables

2016-07-01T20:56:55+00:00

TARGET_FCFLAGS is already added to TARGET_CONFIGURE_OPTS, but was not defined so far. This change fixes this. Cc: Vicente Olivert Riera Signed-off-by: Benjamin Kamath Signed-off-by: Samuel Martin Signed-off-by: Thomas Petazzoni

build: cleanup remaining references to BR2_STRIP_sstrip

2016-06-10T18:15:15+00:00

sstrip option has been removed in commit 106f5b8c5093 ("build: remove deprecated sstrip option"). Signed-off-by: Julien Floret Signed-off-by: Thomas Petazzoni

Config.in: add -Og option

2016-05-24T21:17:52+00:00

-Og (introduced in GCC 4.8) lets you optimize for debugging experience, which can be useful for when you want optimized code that is nonetheless debuggable. Signed-off-by: Martin Kelly Acked-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

package/Makefile.in: adjust LDFLAGS for elf2flt

2016-04-08T12:27:59+00:00

So far, our LDFLAGS for the BR2_BINFMT_FLAT case were only used on Blackfin. However, passing -elf2flt in LDFLAGS is wrong. Indeed, LDFLAGS are not linker flags, but flags passed to the compiler when linking. If you pass -elf2flt to the compiler when linking, it is understood as "-e lf2flt", i.e "the entry point is named lf2flt", which isn't exactly the intention. We in fact need to pass -Wl,-elf2flt in LDFLAGS as well, so that the compiler passes -elf2flt down to the linker. For some reason, this option does not cause an issue with the Blackfin toolchain, but it does with either a Buildroot toolchain for Cortex-M or an OSELAS toolchain for Cortex-M. We have verified that passing -Wl,-elf2flt continues to work with the Blackfin toolchain. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

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