buildroot/support, branch 2016.11

Update for 2016.11

2016-11-30T22:16:22+00:00

Signed-off-by: Peter Korsgaard

core/br2-external: restore compatibility with old distros

2016-11-23T22:31:20+00:00

Currently, the br2-external script uses bash-4's associative arrays. However, some oldish enterprise-class distros like RHEL5 still use bash-3.1 which lacks associative arrays. We restore compatibility with those oldish distros using 'eval' to emulate associative arrays, as suggested by Arnout. Reported-by: Ricardo Martincoski Signed-off-by: "Yann E. MORIN" Cc: Ricardo Martincoski Cc: Thomas De Schampheleire Cc: Arnout Vandecappelle Cc: Max Filippov Reviewed-by: Arnout Vandecappelle (Essensium/Mind) Tested-by: Ricardo Martincoski Signed-off-by: Thomas Petazzoni

pkg-cmake: Change -DNEBUG to -DNDEBUG

2016-11-06T21:30:40+00:00

Signed-off-by: Stefan Nickl Acked-by: Samuel Martin Signed-off-by: Thomas Petazzoni

get-developers: fix parentheses for print

2016-11-05T10:49:05+00:00

Python3 complains about missing parentheses. $ ./support/scripts/get-developers File "./support/scripts/get-developers", line 45 print f ^ SyntaxError: Missing parentheses in call to 'print' Signed-off-by: Gaël PORTAY Signed-off-by: Thomas Petazzoni

linux: add ev3dev extension

2016-11-02T16:52:24+00:00

This adds an ev3dev Linux drivers extension that provides Linux kernel drivers for LEGO MINDSTORMS EV3 from the ev3dev project. Signed-off-by: David Lechner Signed-off-by: Thomas Petazzoni

support/download: make the git wrapper more robust

2016-10-25T21:49:35+00:00

Currently, there are two failure paths in the wrapper: - if the tar fails, then the error is ignored because it is on the left-hand-side of a pipe; - if the find fails, then the error is ignored because it is a process substitution (and there is a pipe, too). While the former could be fixed with "set -o pipefail", the latter can not be fixed thusly and we must use an intemediate file for it. So, fix both issues by using intermediate files, both to generate the list of files to include in the archive, and generate the archive in a temporary tarball. Fixes the following build issue, where the find is failing for whatever unknown reason: http://autobuild.buildroot.net/results/20f/20fd76d2256eee81837f7e9bbaefbe79d7645ae9/ And this one, where the process substitution failed, also for an unknown reason: http://autobuild.buildroot.org/results/018/018971ea9227b386fe25d3c264c7e80b843a9f68/ Signed-off-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

core/graph-depends: add option to graph reverse dependencies

2016-10-25T20:59:05+00:00

Now that we can dump the reverse dependencies of a package, add the ability to graph those. It does not make sense to do a full reverse graph, as it would be semantically equivalent to the direct graph. So we only provide a per-package reverse graph. Signed-off-by: "Yann E. MORIN" Cc: Arnout Vandecappelle Cc: Thomas Petazzoni Signed-off-by: Thomas Petazzoni

scripts/get-developers: correct type of patches argument

2016-10-25T10:43:27+00:00

Current type for 'patches' argument is str. It supposed to only contain names of files. If we specify FileType as type, then we don't need to open file ourself and it allows script to read patch from standard input as well. e.g. $ git show -1 | ./support/scripts/get-developers - Cc: Thomas Petazzoni Signed-off-by: Rahul Bedarkar Signed-off-by: Thomas Petazzoni

toolchainfile.cmake: fix description of CMAKE_Fortran_FLAGS_{DEBUG,RELEASE}

2016-10-22T14:44:06+00:00

Signed-off-by: Thomas Petazzoni

toochainfile.cmake: rework the way Buildroot sets flags

2016-10-22T14:23:44+00:00

From the build configuration, Buildroot defines and set some compiler and linker flags that should be passed to any packages build-system. For package using the cmake-package infrastructure, this is achieved via the toolchainfile.cmake. This change simplifies the way the toolchainfile.cmake file handles these flags: it now just sets them, without any attempt to extend them with those Buildroot defined. This change still allows overriding these flags from the configure command line. So, now, when a CMake-based package needs to extend them, they should be fully set from the package *.mk file. This behavior is consistent with what is done for others package infrastructures. This change should not pull any regression WRT the bug #7280 [1]. However, now, when someone uses the toolchainfile.cmake file outside of Buildroot, he/she must overload all compiler/linker flags (including the ones Buildroot sets since they no longer get automatically added). [1] https://bugs.busybox.net/show_bug.cgi?id=7280 Cc: Arnout Vandecappelle (Essensium/Mind) Cc: Max Filippov Cc: Thomas Petazzoni Signed-off-by: Samuel Martin Reviewed-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni