buildroot/Makefile, branch 2017.11-op-build

Merge tag '2017.11.2' into 2017.11-op-build

2018-01-29T05:01:50+00:00

Release 2017.11.2

Update for 2017.11.2

2018-01-21T21:08:22+00:00

Signed-off-by: Peter Korsgaard

Update for 2017.11.1

2017-12-31T09:03:52+00:00

Signed-off-by: Peter Korsgaard

Separate target-building make targets from image-building make targets

2017-12-01T01:43:34+00:00

Currently, it's not possible to have dependencies from an image-building target to a rootfs-building target. For example, the boot-wrapper-aarch64 package uses the kernel build as an input file. It supplies a dependency on 'linux', but this will break if we're using BR2_TARGET_ROOTFS_INITRAMFS - the wrapper will include the first kernel build, not the rebuild (which contains the embedded initramfs). This means we'd need to express a dependency from the target build to the image build. However, if we do something like: -BOOT_WRAPPER_AARCH64_DEPENDENCIES = linux +BOOT_WRAPPER_AARCH64_DEPENDENCIES = linux26-rebuild-with-initramfs - then we get a circular dependency, because boot-wrapper-aarch64 is in the TARGETS list, which linux26-rebuild-with-initramfs depends on. This change splits the possible targets into two separate lists, TARGET_TARGETS (dependencies for building the target dir) and IMAGE_TARGETS (dependencies for building images). We keep TARGETS as a list of everything, and use TARGET_TARGETS for the rootfs-finalize target. Signed-off-by: Jeremy Kerr [stewart@linux.vnet.ibm.com: update to buildroot 2015.05 changes] Signed-off-by: Stewart Smith Signed-off-by: Joel Stanley

Update for 2017.11

2017-11-30T21:35:17+00:00

Signed-off-by: Peter Korsgaard

Fix makefile include order by using sort/wildcard.

2017-11-23T23:08:23+00:00

The 'include' directive in GNU make supports wildcards, but their expansion has no defined sort order (GLOB_NOSORT is passed to glob()). Usually this doesn't matter. However, there is at least one case where it does make a difference: toolchain/*/*.mk includes both the definitions of the external toolchain packages and pkg-toolchain-external.mk, but pkg-toolchain-external.mk must be included first. For predictability, use ordered 'include $(sort $(wildcard ...))' instead of unordered direct 'include */*.mk' everywhere. Fixes [1] reported by Petr Vorel: make: *** No rule to make target 'toolchain-external-custom', needed by '.../build/toolchain-external/.stamp_configured'. Stop. [1] http://lists.busybox.net/pipermail/buildroot/2017-November/206969.html Signed-off-by: Peter Seiderer Tested-by: Petr Vorel [Arnout: also sort the one remaining include, of the external docs] Signed-off-by: Arnout Vandecappelle (Essensium/Mind)

Update for 2017.11-rc2

2017-11-13T21:28:15+00:00

Signed-off-by: Peter Korsgaard

Update for 2017.11-rc1

2017-11-06T21:03:32+00:00

Signed-off-by: Peter Korsgaard

core/reproducible: do not override SOURCE_DATE_EPOCH

2017-11-05T10:43:19+00:00

SOURCE_DATE_EPOCH is currently forcibly set (to either the git commit date, or the last release date). However, the spec mandates that it should not be modified if already set: https://reproducible-builds.org/specs/source-date-epoch/ Build systems MUST NOT overwrite this variable for child processes to consume if it is already present. Abide by the rule, and only set it if not already set. This will allow users to pass it from an upper-layer buildsystem (e.g. a jenkins or gitlab-ci job, for example), when they have a reson to do so. Reported-by: Peter Korsgaard Reported-by: Einar Jón Gunnarsson Signed-off-by: "Yann E. MORIN" Cc: Peter Korsgaard Cc: Einar Jón Gunnarsson Cc: Thomas Petazzoni Cc: Arnout Vandecappelle Signed-off-by: Peter Korsgaard

Add DEPENDENCIES_HOST_PREREQ to the list of packages

2017-10-22T13:42:26+00:00

That way packages included in that list like ccache will also be regarded as a normal packages for targets like external-deps, show-targets or legal-info Signed-off-by: Alfredo Alvarez Fernandez Signed-off-by: Arnout Vandecappelle (Essensium/Mind)