aboutsummaryrefslogtreecommitdiffstats
path: root/include/u-boot.mk
Commit message (Collapse)AuthorAgeFilesLines
* u-boot.mk: add LOCALVERSION (explicitly specify OpenWrt build)Josef Schlehofer2022-03-061-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For debugging purposes, we need to know if users are using modified U-boot versions or not. Currently, the U-boot version is somehow stripped. This is a little bit problematic when there are backported/wip/to-upstream patches. To make it more confusing, there was (before this commit) two U-boot versioning. U-boot compiled by OpenWrt build bots are missing ``Build:`` This is also the case when the U-boot is compiled locally. Example: ``` U-Boot SPL 2022.01 (Jan 27 2022 - 00:24:34 +0000) U-Boot 2022.01 (Jan 27 2022 - 00:24:34 +0000) ``` On the other hand, if you run full build, you can at least see, where it was compiled. Notice added ``Build:``. Example: ``` U-Boot 2022.01 (Jan 27 2022 - 00:24:34 +0000), Build: jenkins-turris-os-packages-burstlab-omnia-216 ``` In both cases, it is not clear to U-boot developers if it is an unmodified build. This is also caused that there is a missing ``.git`` file from U-boot folder, and so there is no history. It leads to that it can not contain suffix ``-dirty`` (uncommitted modifications) or even something else like number of commits, etc. [1] When U-boot is compiled as it should be, the version should look like this: ``U-Boot 2022.04-rc1-01173-g278195ea1f (Feb 11 2022 - 14:46:50 +0100)`` The date is not changed daily when there are new OpenWrt builds. This commit adds OpenWrt specific version, which could be verified by using strings. ``` $ strings bin/targets/mvebu/cortexa9/u-boot-omnia/u-boot-spl.kwb | grep -E "OpenWrt*" U-Boot SPL 2022.01-OpenWrt-r18942+54-cbfce92367 (Feb 21 2022 - 13:17:34 +0000) arm-openwrt-linux-muslgnueabi-gcc (OpenWrt GCC 11.2.0 r18942+54-cbfce92367) 11.2.0 2022.01-OpenWrt-r18942+54-cbfce92367 U-Boot 2022.01-OpenWrt-r18942+54-cbfce92367 (Feb 21 2022 - 13:17:34 +0000) ``` [1] https://u-boot.readthedocs.io/en/latest/develop/version.html Reported-by: Pali Rohár <pali@kernel.org> Suggested-by: Karel Kočí <karel.koci@nic.cz> [rebased for OpenWrt 21.02] Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com> (cherry picked from commit d6aa9d9e071d9f23ed26f5142991bc66aefe20f5)
* u-boot.mk: switch download to httpsLucian Cristian2020-04-261-1/+2
| | | | | | | ftp can cause problems on some networks switch primary download location to https and add another mirror Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* u-boot.mk: use openwrt url instead of lede projectLuis Araneda2019-08-181-1/+1
| | | | | | | | | The LEDE URL is automatically redirected to the OpenWRT one, returning an HTTP 301 code (Moved Permanently). Also, use https, as indicated by the redirect. Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* u-boot.mk: Fix building of recent U-Boot sourcesPetr Štetiar2019-01-261-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch fixes following error with U-Boot 2019.01 on imx6: In file included from tools/lib/crc16.c:1:0: ./tools/../lib/crc16.c: In function 'crc16_ccitt': ./tools/../lib/crc16.c:70:2: error: 'for' loop initial declarations are only allowed in C99 mode for (int i = 0; i < len; i++) ^ ./tools/../lib/crc16.c:70:2: note: use option -std=c99 or -std=gnu99 to compile your code Code was introduced in the upstream v2019.01-rc1-154-g51c2345: commit 51c2345bd24837f9f67f16268da6dc71573f1325 Author: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Date: Sun Nov 25 19:22:19 2018 +0100 Roll CRC16-CCITT into the hash infrastructure Upstream has added -std=gnu11 host flag in v2018.07-rc2-1-gfa89399: commit fa893990e9b53425af5f5059e04a2bffde91ccf9 Author: Tom Rini <trini@konsulko.com> Date: Tue Jun 19 23:53:54 2018 -0400 Makefile: Ensure we build with -std=gnu11 Build tested on imx6: apalis, mx6sabresd, nitrogen6dl, nitrogen6dl2g, nitrogen6q, nitrogen6q2g, nitrogen6s, nitrogen6s1g, wandboard Run tested: apalis (pending PR #1595) Signed-off-by: Petr Štetiar <ynezz@true.cz>
* u-boot.mk: add HOST_LDFLAGS to UBOOT_MAKE_FLAGSAlexandru Ardelean2018-02-101-1/+1
| | | | | | | | This will make sure that the build system's paths for linking are available. This is needed mostly for linking with tools/libressl. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* u-boot,at91bootstrap: fix incorrect HOSTCPPFLAGS variableAlexandru Ardelean2018-02-101-1/+1
| | | | | | | | | | | | | | | | | This would should up as `$$(HOSTCPPFLAGS)` in the host CFLAGS. ``` make --jobserver-fds=3,4 -j -C <openwrt>/build_dir/target-arm_cortex-a8+vfpv3_musl_eabi/u-boot-A10-OLinuXino-Lime/u-boot-2017.07 CROSS_COMPILE=arm-openwrt-linux-muslgnueabi- DTC="<openwrt>/build_dir/target-arm_cortex-a8+vfpv3_musl_eabi/linux-sunxi_cortexa8/linux-4.9.76/scripts/dtc/dtc" HOSTCC="gcc" HOSTCFLAGS='-O2 -I<openwrt>/staging_dir/host/include -I<openwrt>/staging_dir/host/usr/include -I<openwrt>/staging_dir/hostpkg/include -I<openwrt>/staging_dir/target-arm_cortex-a8+vfpv3_musl_eabi/host/include $$(HOSTCPPFLAGS)' HOSTLDFLAGS="" BL31=<openwrt>/staging_dir/target-arm_cortex-a8+vfpv3_musl_eabi/image/bl31.bin ``` And then it would complain with: ``` /bin/sh: 1: HOSTCPPFLAGS: not found ``` Also, HOSTCPPFLAGS does not exist. The correct var is HOST_CPPFLAGS. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
* u-boot.mk: pass HOSTCC and HOST_CFLAGS into the buildFelix Fietkau2017-04-041-0/+5
| | | | | | | Cuts build time on Mac OS X in half by avoiding repeated $(shell) calls from the build system Signed-off-by: Felix Fietkau <nbd@nbd.name>
* u-boot.mk: add support for overriding DEFAULTFelix Fietkau2017-01-251-0/+2
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* u-boot.mk: add UBOOT_MAKE_FLAGS variable similar to MAKE_FLAGSFelix Fietkau2017-01-251-1/+2
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* build: add generic build template for u-boot packagesFelix Fietkau2017-01-241-0/+96
Signed-off-by: Felix Fietkau <nbd@nbd.name>