summaryrefslogtreecommitdiffstats
path: root/package/nodejs/nodejs.hash
diff options
context:
space:
mode:
authorArnout Vandecappelle <arnout@mind.be>2017-04-10 18:05:11 +0200
committerThomas Petazzoni <thomas.petazzoni@free-electrons.com>2017-04-12 21:42:52 +0200
commitee995b18190aaae11dd4e7b4390c65871c1a1e83 (patch)
treec6bb0ef0490d88698bf02f4f4ff560039673c3ba /package/nodejs/nodejs.hash
parent822b34cb3d8d675f85929b9c46b0c3fac3a361c4 (diff)
downloadbuildroot-ee995b18190aaae11dd4e7b4390c65871c1a1e83.tar.gz
buildroot-ee995b18190aaae11dd4e7b4390c65871c1a1e83.zip
linux: select BR2_PACKAGE_HOST_UBOOT_TOOLS instead of BR2_LINUX_KERNEL_UBOOT_IMAGE
A long time ago, the blind config option BR2_LINUX_KERNEL_UBOOT_IMAGE was introduced to be able to trigger the linux -> host-uboot-tools dependency. Back in those days, there was no user-configurable BR2_PACKAGE_HOST_UBOOT_TOOLS. Now, however, it is possible to select a custom kernel image name that needs uboot-tools, and manually enable BR2_PACKAGE_HOST_UBOOT_TOOLS. In this case, however, the linux -> host-uboot-tools is missed and the build is not reproducible. An example of such a situation is the upcoming CI40 defconfig. As a solution, remove BR2_LINUX_KERNEL_UBOOT_IMAGE entirely. Instead, just select BR2_PACKAGE_HOST_UBOOT_TOOLS and add the dependency if it is selected. Note that this may introduce a redundant dependency in case the user selected BR2_PACKAGE_HOST_UBOOT_TOOLS for some other reason (e.g. to be able to generate a U-Boot environment to include in the image, while the kernel is built as a zImage). However, the redundant dependency shouldn't hurt much. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Cc: Abhimanyu Vishwakarma <abhimanyu.v@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Diffstat (limited to 'package/nodejs/nodejs.hash')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud