u-boot: Update to 2016.09.01 release
PATCH 1/4 u-boot: Update to 2016.09.01 release
Upgrade U-Boot to the latest version.
---
.../{u-boot-common_2016.03.inc => u-boot-common_2016.09.01.inc} | 8 ++++----
.../{u-boot-fw-utils_2016.03.bb => u-boot-fw-utils_2016.09.01.bb} | 0
.../{u-boot-mkimage_2016.03.bb => u-boot-mkimage_2016.09.01.bb} | 0
.../u-boot/{u-boot_2016.03.bb => u-boot_2016.09.01.bb} | 0
4 files changed, 4 insertions(+), 4 deletions(-)
rename meta/recipes-bsp/u-boot/{u-boot-common_2016.03.inc => u-boot-common_2016.09.01.inc} (59%)
rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2016.03.bb => u-boot-fw-utils_2016.09.01.bb} (100%)
rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2016.03.bb => u-boot-mkimage_2016.09.01.bb} (100%)
rename meta/recipes-bsp/u-boot/{u-boot_2016.03.bb => u-boot_2016.09.01.bb} (100%)meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc renamed from meta/recipes-bsp/u-boot/u-boot-common_2016.03.inc +4 -4
@@ -4,13 +4,13 @@ SECTION = "bootloaders" LICENSE = "GPLv2+" LIC_FILES_CHKSUM = "file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6" -# This revision corresponds to the tag "v2016.03" +# This revision corresponds to the tag "v2016.09.01" # We use the revision in order to avoid having to fetch it from the # repo during parse -SRCREV = "df61a74e6845ec9bdcdd48d2aff5e9c2c6debeaa" +SRCREV = "f3363c060497515ca8b71451cb56f3ec0abacaa9" -PV = "v2016.03+git${SRCPV}" +PV = "v2016.09.01+git${SRCPV}" -SRC_URI = "git://git.denx.de/u-boot.git;branch=master" +SRC_URI = "git://git.denx.de/u-boot.git;branch=u-boot-2016.09.y" S = "${WORKDIR}/git"
meta/recipes-bsp/u-boot/u-boot-fw-utils_2016.09.01.bb renamed from meta/recipes-bsp/u-boot/u-boot-fw-utils_2016.03.bb +0 -0
meta/recipes-bsp/u-boot/u-boot-mkimage_2016.09.01.bb renamed from meta/recipes-bsp/u-boot/u-boot-mkimage_2016.03.bb +0 -0
meta/recipes-bsp/u-boot/u-boot_2016.09.01.bb renamed from meta/recipes-bsp/u-boot/u-boot_2016.03.bb +0 -0
Signature · 1 line
2.9.3
PATCH 2/4 u-boot: Drop the +git part from PV
The U-Boot package is using release versions of U-Boot, so drop the extra +git part from PV.
--- meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc +1 -1
@@ -9,7 +9,7 @@ LIC_FILES_CHKSUM = "file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6" # repo during parse SRCREV = "f3363c060497515ca8b71451cb56f3ec0abacaa9" -PV = "v2016.09.01+git${SRCPV}" +PV = "v2016.09.01" SRC_URI = "git://git.denx.de/u-boot.git;branch=u-boot-2016.09.y"
Signature · 1 line
2.9.3
Re: [PATCH 2/4] u-boot: Drop the +git part from PV
Quoted 6 lines · Marek Vasut
The U-Boot package is using release versions of U-Boot, so drop the extra +git part from PV.
Signed-off-by Marek Vasut <[email protected]>Cc Richard Purdie <[email protected]>Cc Denys Dmytriyenko <[email protected]>
Quoted 20 lines
--- meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc +1
-1@@ -9,7 +9,7 @@ LIC_FILES_CHKSUM = "file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6" # repo during parse SRCREV = "f3363c060497515ca8b71451cb56f3ec0abacaa9" -PV = "v2016.09.01+git${SRCPV}" +PV = "v2016.09.01" SRC_URI = "git://git.denx.de/u-boot.git;branch=u-boot-2016.09.y"Signature · 1 line
2.9.3
PATCH 4/4 u-boot: Drop redundant comment
In reply to Marek VasutDrop comment stating that the SRCREV corresponds to particular U-Boot version. This comment is redundant, since the U-Boot version is part of the recipe filename.
--- meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc | 1 - 1 file changed, 1 deletion(-)
meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc +0 -1
@@ -5,7 +5,6 @@ LICENSE = "GPLv2+" LIC_FILES_CHKSUM = "file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6" PE="1" -# This revision corresponds to the tag "v2016.09.01" # We use the revision in order to avoid having to fetch it from the # repo during parse SRCREV = "f3363c060497515ca8b71451cb56f3ec0abacaa9"
Signature · 1 line
2.9.3
Re: [PATCH 4/4] u-boot: Drop redundant comment
Quoted 7 lines · Marek Vasut
Drop comment stating that the SRCREV corresponds to particular U-Boot version. This comment is redundant, since the U-Boot version is part of the recipe filename.
Signed-off-by Marek Vasut <[email protected]>Cc Richard Purdie <[email protected]>Cc Denys Dmytriyenko <[email protected]>
Quoted 19 lines
--- meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc | 1 - 1 file changed, 1 deletion(-)meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc +0
-1@@ -5,7 +5,6 @@ LICENSE = "GPLv2+" LIC_FILES_CHKSUM = "file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6" PE="1" -# This revision corresponds to the tag "v2016.09.01" # We use the revision in order to avoid having to fetch it from the # repo during parse SRCREV = "f3363c060497515ca8b71451cb56f3ec0abacaa9"Signature · 1 line
2.9.3
PATCH v2 3/4 u-boot: Drop PV altogether
In reply to Marek VasutDrop the explicit setting of PV altogether. This changes the U-Boot version string from "v20yy.mm" to "20yy.mm" , so layer setting the PREFERRED_VERSION_u-boot must be updated by removing the leading 'v'.
---
V2: - Add PE=1 to increment the epoch of the package, as the version
numbering changes in non-backward-compatible way.
--- meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc +1 -2
@@ -3,14 +3,13 @@ SECTION = "bootloaders" LICENSE = "GPLv2+" LIC_FILES_CHKSUM = "file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6" +PE="1" # This revision corresponds to the tag "v2016.09.01" # We use the revision in order to avoid having to fetch it from the # repo during parse SRCREV = "f3363c060497515ca8b71451cb56f3ec0abacaa9" -PV = "v2016.09.01" - SRC_URI = "git://git.denx.de/u-boot.git;branch=u-boot-2016.09.y" S = "${WORKDIR}/git"
Signature · 1 line
2.9.3
Re: [PATCH V2 3/4] u-boot: Drop PV altogether
Quoted 7 lines · Marek Vasut
Drop the explicit setting of PV altogether. This changes the U-Boot version string from "v20yy.mm" to "20yy.mm" , so layer setting the PREFERRED_VERSION_u-boot must be updated by removing the leading 'v'.
Signed-off-by Marek Vasut <[email protected]>Cc Richard Purdie <[email protected]>Cc Denys Dmytriyenko <[email protected]>
Quoted 12 lines
---
V2: - Add PE=1 to increment the epoch of the package, as the version
numbering changes in non-backward-compatible way.--- meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc +0
-0
meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc SECTION = "bootloaders" · line 6
Quoted 4 lines
meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc +1
-0@@ -3,14 +3,13 @@ SECTION = "bootloaders" LICENSE = "GPLv2+" LIC_FILES_CHKSUM = "file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6" +PE="1"
^^^^^^^^
Formatting! My OCD is going to kill me... :)
Quoted 13 lines
meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc +0
-2# This revision corresponds to the tag "v2016.09.01" # We use the revision in order to avoid having to fetch it from the # repo during parse SRCREV = "f3363c060497515ca8b71451cb56f3ec0abacaa9" -PV = "v2016.09.01" - SRC_URI = "git://git.denx.de/u-boot.git;branch=u-boot-2016.09.y" S = "${WORKDIR}/git"Signature · 1 line
2.9.3
PATCH v3 3/4 u-boot: Drop PV altogether
In reply to Marek VasutDrop the explicit setting of PV altogether. This changes the U-Boot version string from "v20yy.mm" to "20yy.mm" , so layer setting the PREFERRED_VERSION_u-boot must be updated by removing the leading 'v'.
---
V2: - Add PE=1 to increment the epoch of the package, as the version
numbering changes in non-backward-compatible way.
V3: - Formatting fix of the PE line
--- meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc +1 -2
@@ -3,14 +3,13 @@ SECTION = "bootloaders" LICENSE = "GPLv2+" LIC_FILES_CHKSUM = "file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6" +PE = "1" # This revision corresponds to the tag "v2016.09.01" # We use the revision in order to avoid having to fetch it from the # repo during parse SRCREV = "f3363c060497515ca8b71451cb56f3ec0abacaa9" -PV = "v2016.09.01" - SRC_URI = "git://git.denx.de/u-boot.git;branch=u-boot-2016.09.y" S = "${WORKDIR}/git"
Signature · 1 line
2.9.3
Re: [PATCH V3 3/4] u-boot: Drop PV altogether
Quoted 7 lines · Marek Vasut
Drop the explicit setting of PV altogether. This changes the U-Boot version string from "v20yy.mm" to "20yy.mm" , so layer setting the PREFERRED_VERSION_u-boot must be updated by removing the leading 'v'.
Signed-off-by Marek Vasut <[email protected]>Cc Richard Purdie <[email protected]>Cc Denys Dmytriyenko <[email protected]>
Quoted 4 lines
---
V2: - Add PE=1 to increment the epoch of the package, as the version
numbering changes in non-backward-compatible way.
V3: - Formatting fix of the PE line
Thanks!
Quoted 27 lines
--- meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc +1
-2@@ -3,14 +3,13 @@ SECTION = "bootloaders" LICENSE = "GPLv2+" LIC_FILES_CHKSUM = "file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6" +PE = "1" # This revision corresponds to the tag "v2016.09.01" # We use the revision in order to avoid having to fetch it from the # repo during parse SRCREV = "f3363c060497515ca8b71451cb56f3ec0abacaa9" -PV = "v2016.09.01" - SRC_URI = "git://git.denx.de/u-boot.git;branch=u-boot-2016.09.y" S = "${WORKDIR}/git"Signature · 1 line
2.9.3
Quoted 5 lines · Marek Vasut
Upgrade U-Boot to the latest version.
Signed-off-by Marek Vasut <[email protected]>Cc Richard Purdie <[email protected]>Cc Denys Dmytriyenko <[email protected]>
Quoted 51 lines
--- .../{u-boot-common_2016.03.inc => u-boot-common_2016.09.01.inc} | 8 ++++---- .../{u-boot-fw-utils_2016.03.bb => u-boot-fw-utils_2016.09.01.bb} | 0 .../{u-boot-mkimage_2016.03.bb => u-boot-mkimage_2016.09.01.bb} | 0 .../u-boot/{u-boot_2016.03.bb => u-boot_2016.09.01.bb} | 0 4 files changed, 4 insertions(+), 4 deletions(-) rename meta/recipes-bsp/u-boot/{u-boot-common_2016.03.inc => u-boot-common_2016.09.01.inc} (59%) rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2016.03.bb => u-boot-fw-utils_2016.09.01.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2016.03.bb => u-boot-mkimage_2016.09.01.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot_2016.03.bb => u-boot_2016.09.01.bb} (100%)meta/recipes-bsp/u-boot/u-boot-common_2016.09.01.inc renamed from meta/recipes-bsp/u-boot/u-boot-common_2016.03.inc +4
-4@@ -4,13 +4,13 @@ SECTION = "bootloaders" LICENSE = "GPLv2+" LIC_FILES_CHKSUM = "file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6" -# This revision corresponds to the tag "v2016.03" +# This revision corresponds to the tag "v2016.09.01" # We use the revision in order to avoid having to fetch it from the # repo during parse -SRCREV = "df61a74e6845ec9bdcdd48d2aff5e9c2c6debeaa" +SRCREV = "f3363c060497515ca8b71451cb56f3ec0abacaa9" -PV = "v2016.03+git${SRCPV}" +PV = "v2016.09.01+git${SRCPV}" -SRC_URI = "git://git.denx.de/u-boot.git;branch=master" +SRC_URI = "git://git.denx.de/u-boot.git;branch=u-boot-2016.09.y" S = "${WORKDIR}/git"meta/recipes-bsp/u-boot/u-boot-fw-utils_2016.09.01.bb renamed from meta/recipes-bsp/u-boot/u-boot-fw-utils_2016.03.bb +0
-0meta/recipes-bsp/u-boot/u-boot-mkimage_2016.09.01.bb renamed from meta/recipes-bsp/u-boot/u-boot-mkimage_2016.03.bb +0
-0meta/recipes-bsp/u-boot/u-boot_2016.09.01.bb renamed from meta/recipes-bsp/u-boot/u-boot_2016.03.bb +0
-0Signature · 1 line
2.9.3
Quoted 2 lines · Marek Vasut
Upgrade U-Boot to the latest version.
I hope nobody objects but I squashed these for clarity.
Ross
Quoted 8 lines · Ross
On 20 October 2016 at 14:35, Marek Vasut <[email protected] <mailto:[email protected]>> wrote:
Upgrade U-Boot to the latest version.
I hope nobody objects but I squashed these for clarity.
All right ;-)
Signature · 2 lines
Best regards, Marek Vasut
Quoted 2 lines · Marek Vasut
Upgrade U-Boot to the latest version.
As usual, u-boot-mkimage broke again:
| DEBUG: Executing shell function do_compile
| x86_64-poky-linux-gcc -m64 -march=core2 -mtune=core2 -msse3
-mfpmath=sse
--sysroot=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/sysroots/qemux86-64
-O2 -pipe -g -feliminate-unused-debug-types
-fdebug-prefix-map=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/work/core2-64-poky-linux/u-boot-mkimage/1_2016.09.01-r0=/usr/src/debug/u-boot-mkimage/1_2016.09.01-r0 -fdebug-prefix-map=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/sysroots/x86_64-linux= -fdebug-prefix-map=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/sysroots/qemux86-64=
-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wp,-MD,tools/.bin2header.d
-Wall -Wstrict-prototypes -O2 -fomit-frame-pointer
-DCONFIG_FIT_SIGNATURE -include ./include/libfdt_env.h -idirafterinclude
-idirafter./arch/sandbox/include -I./lib/libfdt -I./tools
-DCONFIG_SYS_TEXT_BASE=0 -DUSE_HOSTCC -D__KERNEL_STRICT_NAMES -D_GNU_SOURCE
-o tools/bin2header tools/bin2header.c
| cat ./Licenses/gpl-2.0.txt | gzip -9 -c | \ | tools/bin2header license_gzip > ./include/license.h | x86_64-poky-linux-gcc -m64 -march=core2 -mtune=core2 -msse3
-mfpmath=sse
--sysroot=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/sysroots/qemux86-64
-O2 -pipe -g -feliminate-unused-debug-types
-fdebug-prefix-map=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/work/core2-64-poky-linux/u-boot-mkimage/1_2016.09.01-r0=/usr/src/debug/u-boot-mkimage/1_2016.09.01-r0 -fdebug-prefix-map=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/sysroots/x86_64-linux= -fdebug-prefix-map=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/sysroots/qemux86-64=
-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wp,-MD,tools/lib/.crc32.o.d
-Wall -Wstrict-prototypes -O2 -fomit-frame-pointer
-DCONFIG_FIT_SIGNATURE -include ./include/libfdt_env.h -idirafterinclude
-idirafter./arch/sandbox/include -I./lib/libfdt -I./tools
-DCONFIG_SYS_TEXT_BASE=0 -DUSE_HOSTCC -D__KERNEL_STRICT_NAMES -D_GNU_SOURCE
-pedantic -c -o tools/lib/crc32.o tools/lib/crc32.c
| /bin/sh: tools/bin2header: /lib/ld-linux-x86-64.so.2: bad ELF
interpreter: No such file or directory
| ERROR: oe_runmake failed
| make[1]: *** [include/license.h] Error 126
NOTE: recipe u-boot-mkimage-1_2016.09.01-r0: task do_compile: Failed
ERROR: Task
(/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/meta/recipes-bsp/u-boot/u-boot-mkimage_2016.09.01.bb:do_compile)
failed with exit code '1'
It's using the target compiler/sysroot/options to build a runtime tool (so should use BUILD_CC instead of CC, etc).
Ross
On 10/21/2016 09:47 AM, Burton, Ross wrote:
Hi!
Quoted 7 lines
On 20 October 2016 at 14:35, Marek Vasut <[email protected] <mailto:[email protected]>> wrote:
Upgrade U-Boot to the latest version.
As usual, u-boot-mkimage broke again:
That's weird, I successfully built it for nios2 during my tests. Can you tell me how I can replicate the issue , so I can test for it to prevent regression and roll out a patch ?
Quoted 44 lines
| DEBUG: Executing shell function
do_compile
| x86_64-poky-linux-gcc -m64 -march=core2 -mtune=core2 -msse3(quoted diff) +0
-7-mfpmath=sse --sysroot=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/sysroots/qemux86-64 -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/work/core2-64-poky-linux/u-boot-mkimage/1_2016.09.01-r0=/usr/src/debug/u-boot-mkimage/1_2016.09.01-r0 -fdebug-prefix-map=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/sysroots/x86_64-linux= -fdebug-prefix-map=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/sysroots/qemux86-64= -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wp,-MD,tools/.bin2header.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -DCONFIG_FIT_SIGNATURE -include
./include/libfdt_env.h-idirafterinclude(quoted diff) +0
-3-idirafter./arch/sandbox/include -I./lib/libfdt -I./tools -DCONFIG_SYS_TEXT_BASE=0 -DUSE_HOSTCC -D__KERNEL_STRICT_NAMES -D_GNU_SOURCE -o tools/bin2header tools/bin2header.c| cat ./Licenses/gpl-2.0.txt | gzip -9 -c | \ | tools/bin2header license_gzip > ./include/license.h | x86_64-poky-linux-gcc -m64 -march=core2 -mtune=core2 -msse3(quoted diff) +0
-7-mfpmath=sse --sysroot=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/sysroots/qemux86-64 -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/work/core2-64-poky-linux/u-boot-mkimage/1_2016.09.01-r0=/usr/src/debug/u-boot-mkimage/1_2016.09.01-r0 -fdebug-prefix-map=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/sysroots/x86_64-linux= -fdebug-prefix-map=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/sysroots/qemux86-64= -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wp,-MD,tools/lib/.crc32.o.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -DCONFIG_FIT_SIGNATURE -include
./include/libfdt_env.h-idirafterinclude(quoted diff) +0
-3-idirafter./arch/sandbox/include -I./lib/libfdt -I./tools -DCONFIG_SYS_TEXT_BASE=0 -DUSE_HOSTCC -D__KERNEL_STRICT_NAMES -D_GNU_SOURCE -pedantic -c -o tools/lib/crc32.o tools/lib/crc32.c|
/bin/sh:tools/bin2header:/lib/ld-linux-x86-64.so.2: bad ELF
interpreter: No such file or directory
| ERROR:oe_runmakefailed
| make[1]: *** [include/license.h] Error 126
NOTE: recipe u-boot-mkimage-1_2016.09.01-r0: taskdo_compile: Failed
ERROR: Task (/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/meta/recipes-bsp/u-boot/u-boot-mkimage_2016.09.01.bb:do_compile) failed with exit code '1'It's using the target compiler/sysroot/options to build a runtime tool (so should use
BUILD_CCinstead of CC, etc).Ross
Signature · 2 lines
Best regards, Marek Vasut
Quoted 7 lines · Marek Vasut
On 10/21/2016 09:47 AM, Burton, Ross wrote:
Hi!
Quoted 3 lines
On 20 October 2016 at 14:35, Marek Vasut <[email protected] <mailto:[email protected]>> wrote:
Quoted 8 lines
Quoted 4 lines
Upgrade U-Boot to the latest version.
As usual, u-boot-mkimage broke again:
That's weird, I successfully built it for nios2 during my tests. Can you tell me how I can replicate the issue , so I can test for it to prevent regression and roll out a patch ?
Marek, Ross,
Any progress on this? Need any help testing?
Signature · 1 line
Denys
Quoted 54 lines
Quoted 44 lines
| DEBUG: Executing shell function
do_compile
| x86_64-poky-linux-gcc -m64 -march=core2 -mtune=core2 -msse3(quoted diff) +0
-7-mfpmath=sse --sysroot=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/sysroots/qemux86-64 -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/work/core2-64-poky-linux/u-boot-mkimage/1_2016.09.01-r0=/usr/src/debug/u-boot-mkimage/1_2016.09.01-r0 -fdebug-prefix-map=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/sysroots/x86_64-linux= -fdebug-prefix-map=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/sysroots/qemux86-64= -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wp,-MD,tools/.bin2header.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -DCONFIG_FIT_SIGNATURE -include
./include/libfdt_env.h-idirafterinclude(quoted diff) +0
-3-idirafter./arch/sandbox/include -I./lib/libfdt -I./tools -DCONFIG_SYS_TEXT_BASE=0 -DUSE_HOSTCC -D__KERNEL_STRICT_NAMES -D_GNU_SOURCE -o tools/bin2header tools/bin2header.c| cat ./Licenses/gpl-2.0.txt | gzip -9 -c | \ | tools/bin2header license_gzip > ./include/license.h | x86_64-poky-linux-gcc -m64 -march=core2 -mtune=core2 -msse3(quoted diff) +0
-7-mfpmath=sse --sysroot=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/sysroots/qemux86-64 -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/work/core2-64-poky-linux/u-boot-mkimage/1_2016.09.01-r0=/usr/src/debug/u-boot-mkimage/1_2016.09.01-r0 -fdebug-prefix-map=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/sysroots/x86_64-linux= -fdebug-prefix-map=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/sysroots/qemux86-64= -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wp,-MD,tools/lib/.crc32.o.d -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -DCONFIG_FIT_SIGNATURE -include
./include/libfdt_env.h-idirafterinclude(quoted diff) +0
-3-idirafter./arch/sandbox/include -I./lib/libfdt -I./tools -DCONFIG_SYS_TEXT_BASE=0 -DUSE_HOSTCC -D__KERNEL_STRICT_NAMES -D_GNU_SOURCE -pedantic -c -o tools/lib/crc32.o tools/lib/crc32.c|
/bin/sh:tools/bin2header:/lib/ld-linux-x86-64.so.2: bad ELF
interpreter: No such file or directory
| ERROR:oe_runmakefailed
| make[1]: *** [include/license.h] Error 126
NOTE: recipe u-boot-mkimage-1_2016.09.01-r0: taskdo_compile: Failed
ERROR: Task (/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/meta/recipes-bsp/u-boot/u-boot-mkimage_2016.09.01.bb:do_compile) failed with exit code '1'It's using the target compiler/sysroot/options to build a runtime tool (so should use
BUILD_CCinstead of CC, etc).Ross
Signature · 7 lines
Best regards, Marek Vasut -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 13 lines · Denys Dmytriyenko
Quoted 12 lines · Marek Vasut
On 10/21/2016 09:47 AM, Burton, Ross wrote:
Hi!
Quoted 7 lines
On 20 October 2016 at 14:35, Marek Vasut <[email protected] <mailto:[email protected]>> wrote:
Upgrade U-Boot to the latest version.
As usual, u-boot-mkimage broke again:
Quoted 8 lines
Quoted 3 lines
That's weird, I successfully built it for nios2 during my tests. Can you tell me how I can replicate the issue , so I can test for it to prevent regression and roll out a patch ?
Marek, Ross,
Any progress on this? Need any help testing?
Yeah, how do you replicate this issue ?
Signature · 2 lines
Best regards, Marek Vasut
Quoted 18 lines · Marek Vasut
Quoted 17 lines · Denys Dmytriyenko
Quoted 15 lines · Marek Vasut
On 10/21/2016 09:47 AM, Burton, Ross wrote:
Hi!
Quoted 7 lines
On 20 October 2016 at 14:35, Marek Vasut <[email protected] <mailto:[email protected]>> wrote:
Upgrade U-Boot to the latest version.
As usual, u-boot-mkimage broke again:
That's weird, I successfully built it for nios2 during my tests. Can you tell me how I can replicate the issue , so I can test for it to prevent regression and roll out a patch ?
Quoted 6 lines
Quoted 4 lines
Marek, Ross,
Any progress on this? Need any help testing?
Yeah, how do you replicate this issue ?
Hi!
I am just looking at a similar problem and want to jump into the discussion. As Ross said, the problem is to not respect host/target -- cc/cflags/ldflags. So to replicate the issue, you can use a bare minimum build host with no cross toolchain installed, and I guess all targets will fail to build. As this has been broken so many times, I want to discuss some possible fixes:
In the top level Makefile we have:
HOSTCC = cc
HOSTCFLAGS = ...
The problem is, you cannot properly override those variables, as they get used a lot to do different things, e.g. in tools/Makefile we have (for cross tools target) HOSTCC = $(CC) and for HOSTCFLAGS we have appends for configuration. Thats why we have the current workaround with a squashed override. I see many possible solutions and would like to hear your opinion:
1. Make top level Makefile HOST assignments conditional "?="
- easy
- will probably not be accepted upstream
2. add "override" to appends in sublevel Makefiles
- adds complexity/one level of override hierarchy
3. Don't use appends for those variables (like in the kernel Makefile), overrides in the recipe
- clean
- quite some rework in uboot
4. Hack around in the recipe with class overrides and exports
- quickfix, no patch required
- fails easily in the future
Any thoughts?
Stefan
Quoted 19 lines · Stefan Müller-Klieser
Quoted 18 lines · Marek Vasut
Quoted 17 lines · Denys Dmytriyenko
Quoted 15 lines · Marek Vasut
On 10/21/2016 09:47 AM, Burton, Ross wrote:
Hi!
Quoted 7 lines
On 20 October 2016 at 14:35, Marek Vasut <[email protected] <mailto:[email protected]>> wrote:
Upgrade U-Boot to the latest version.
As usual, u-boot-mkimage broke again:
That's weird, I successfully built it for nios2 during my tests. Can you tell me how I can replicate the issue , so I can test for it to prevent regression and roll out a patch ?
Quoted 7 lines
Quoted 6 lines
Quoted 4 lines
Marek, Ross,
Any progress on this? Need any help testing?
Yeah, how do you replicate this issue ?
Hi!
Hi!
Quoted 4 lines
I am just looking at a similar problem and want to jump into the discussion. As Ross said, the problem is to not respect host/target -- cc/cflags/ldflags. So to replicate the issue, you can use a bare minimum build host with no cross toolchain installed, and I guess all targets will fail to build.
Well both ARM and nios2 builds for me, so I wonder what sort of stupid thing am I doing.
Quoted 4 lines
As this has been broken so many times, I want to discuss some possible fixes:
In the top levelMakefilewe have:
HOSTCC = cc
HOSTCFLAGS = ...
Quoted 8 lines
The problem is, you cannot properly override those variables, as they get used a lot to do different things, e.g. in
tools/Makefilewe have (for cross tools target) HOSTCC = $(CC) and for HOSTCFLAGS we have appends for configuration. Thats why we have the current workaround with a squashed override. I see many possible solutions and would like to hear your opinion:
1. Make top levelMakefileHOST assignments conditional "?="
- easy
- will probably not be accepted upstream
Why ?
Quoted 6 lines
2. add "override" to appends in sublevel Makefiles
- adds complexity/one level of override hierarchy
3. Don't use appends for those variables (like in the kernelMakefile), overrides in the recipe
- clean
- quite some rework in uboot
Can you provide details ?
Quoted 7 lines
4. Hack around in the recipe with class overrides and exports
- quickfix, no patch required
- fails easily in the futureAny thoughts?
Stefan
Signature · 2 lines
Best regards, Marek Vasut
Quoted 30 lines · Marek Vasut
Quoted 19 lines · Stefan Müller-Klieser
Quoted 18 lines · Marek Vasut
Quoted 17 lines · Denys Dmytriyenko
Quoted 15 lines · Marek Vasut
On 10/21/2016 09:47 AM, Burton, Ross wrote:
Hi!
Quoted 7 lines
On 20 October 2016 at 14:35, Marek Vasut <[email protected] <mailto:[email protected]>> wrote:
Upgrade U-Boot to the latest version.
As usual, u-boot-mkimage broke again:
That's weird, I successfully built it for nios2 during my tests. Can you tell me how I can replicate the issue , so I can test for it to prevent regression and roll out a patch ?
Quoted 7 lines
Quoted 6 lines
Quoted 4 lines
Marek, Ross,
Any progress on this? Need any help testing?
Yeah, how do you replicate this issue ?
Hi!
Hi!
Quoted 7 lines
Quoted 4 lines
I am just looking at a similar problem and want to jump into the discussion. As Ross said, the problem is to not respect host/target -- cc/cflags/ldflags. So to replicate the issue, you can use a bare minimum build host with no cross toolchain installed, and I guess all targets will fail to build.
Well both ARM and nios2 builds for me, so I wonder what sort of stupid thing am I doing.
Well, that's the thing - your patches didn't change anything around toolchain, so it shouldn't break what used to be working before, right? Unless it was already broken...
Ross,
Care to elaborate on what is breaking for you and what setup you are using?
Quoted 13 lines
Quoted 4 lines
As this has been broken so many times, I want to discuss some possible fixes:
In the top levelMakefilewe have:
HOSTCC = cc
HOSTCFLAGS = ...Quoted 8 lines
The problem is, you cannot properly override those variables, as they get used a lot to do different things, e.g. in
tools/Makefilewe have (for cross tools target) HOSTCC = $(CC) and for HOSTCFLAGS we have appends for configuration. Thats why we have the current workaround with a squashed override. I see many possible solutions and would like to hear your opinion:
1. Make top levelMakefileHOST assignments conditional "?="
- easy
- will probably not be accepted upstream
Quoted 1 line
Why ?
Heh, good one! :)
Quoted 22 lines
Quoted 6 lines
2. add "override" to appends in sublevel Makefiles
- adds complexity/one level of override hierarchy
3. Don't use appends for those variables (like in the kernelMakefile), overrides in the recipe
- clean
- quite some rework in ubootCan you provide details ?
Quoted 7 lines
4. Hack around in the recipe with class overrides and exports
- quickfix, no patch required
- fails easily in the futureAny thoughts?
StefanSignature · 2 lines
Best regards, Marek Vasut
Quoted 36 lines · Denys Dmytriyenko
Quoted 35 lines · Marek Vasut
Quoted 19 lines · Stefan Müller-Klieser
Quoted 18 lines · Marek Vasut
Quoted 17 lines · Denys Dmytriyenko
Quoted 15 lines · Marek Vasut
On 10/21/2016 09:47 AM, Burton, Ross wrote:
Hi!
Quoted 7 lines
On 20 October 2016 at 14:35, Marek Vasut <[email protected] <mailto:[email protected]>> wrote:
Upgrade U-Boot to the latest version.
As usual, u-boot-mkimage broke again:
That's weird, I successfully built it for nios2 during my tests. Can you tell me how I can replicate the issue , so I can test for it to prevent regression and roll out a patch ?
Quoted 7 lines
Quoted 6 lines
Quoted 4 lines
Marek, Ross,
Any progress on this? Need any help testing?
Yeah, how do you replicate this issue ?
Hi!
Hi!
Quoted 4 lines
I am just looking at a similar problem and want to jump into the discussion. As Ross said, the problem is to not respect host/target -- cc/cflags/ldflags. So to replicate the issue, you can use a bare minimum build host with no cross toolchain installed, and I guess all targets will fail to build.
Quoted 6 lines
Quoted 2 lines
Well both ARM and nios2 builds for me, so I wonder what sort of stupid thing am I doing.
Well, that's the thing - your patches didn't change anything around toolchain, so it shouldn't break what used to be working before, right? Unless it was already broken...
That's correct ... unless it got broken between 2016.03 and 2016.09 in U-Boot upstream.
Quoted 3 lines
Ross,
Care to elaborate on what is breaking for you and what setup you are using?
Please do, indeed.
Quoted 40 lines
Quoted 13 lines
Quoted 4 lines
As this has been broken so many times, I want to discuss some possible fixes:
In the top levelMakefilewe have:
HOSTCC = cc
HOSTCFLAGS = ...Quoted 8 lines
The problem is, you cannot properly override those variables, as they get used a lot to do different things, e.g. in
tools/Makefilewe have (for cross tools target) HOSTCC = $(CC) and for HOSTCFLAGS we have appends for configuration. Thats why we have the current workaround with a squashed override. I see many possible solutions and would like to hear your opinion:
1. Make top levelMakefileHOST assignments conditional "?="
- easy
- will probably not be accepted upstreamQuoted 1 line
Why ?
Heh, good one! :)
Quoted 22 lines
Quoted 6 lines
2. add "override" to appends in sublevel Makefiles
- adds complexity/one level of override hierarchy
3. Don't use appends for those variables (like in the kernelMakefile), overrides in the recipe
- clean
- quite some rework in ubootCan you provide details ?
Quoted 7 lines
4. Hack around in the recipe with class overrides and exports
- quickfix, no patch required
- fails easily in the futureAny thoughts?
StefanSignature · 2 lines
Best regards, Marek Vasut
Signature · 2 lines
Best regards, Marek Vasut
Quoted 6 lines · Marek Vasut
Quoted 3 lines
Ross,
Care to elaborate on what is breaking for you and what setup you are
using?
Please do, indeed.
Sorry, I was away for a week and my out-of-office only fires for @intel.com senders to avoid spamming the mailing list. :)
This was doing a build of *target* u-boot-mkimage for qemux86-64. I suspect that this autobuilder was running on Debian as Debian doesn't have a /lib/lib-linux-x86-64 but oe-core does, so a binary built for x86-64 oe-core may work on some distributions but not others.
Ross
Quoted 11 lines · Ross
Quoted 3 lines · On 28 October 2016 at 03:14, Marek Vasut <[email protected]…
Ross,
Care to elaborate on what is breaking for you and what setup you are using?
Please do, indeed.
Quoted 7 lines
Sorry, I was away for a week and my out-of-office only fires for @intel.com <http://intel.com> senders to avoid spamming the mailing list. :)
This was doing a build of *target* u-boot-mkimage for qemux86-64. I suspect that this autobuilder was running on Debian as Debian doesn't have a
/lib/lib-linux-x86-64but oe-core does, so a binary built for x86-64 oe-core may work on some distributions but not others.
So the simplest test would be to do the build of native u-boot-mkimage on, say, centos/fedora ?
Signature · 2 lines
Best regards, Marek Vasut
Quoted 3 lines · Marek Vasut
So the simplest test would be to do the build of native u-boot-mkimage on, say, centos/fedora ?
No, a build on Debian (I've just replicated this on my own debian build machine). Literally just "bitbake u-boot-mkimage" fails to build.
Ross
Quoted 10 lines · Ross
On 30 October 2016 at 18:18, Marek Vasut <[email protected] <mailto:[email protected]>> wrote:
So the simplest test would be to do the build of native u-boot-mkimage on, say, centos/fedora ?
No, a build on Debian (I've just replicated this on my own debian build machine). Literally just "bitbake u-boot-mkimage" fails to build.
Got it, replicated, thanks.
I sent a patch, see if that works for you.
Signature · 2 lines
Best regards, Marek Vasut
Quoted 33 lines · Marek Vasut
Quoted 19 lines · Stefan Müller-Klieser
Quoted 18 lines · Marek Vasut
Quoted 17 lines · Denys Dmytriyenko
Quoted 15 lines · Marek Vasut
On 10/21/2016 09:47 AM, Burton, Ross wrote:
Hi!
Quoted 7 lines
On 20 October 2016 at 14:35, Marek Vasut <[email protected] <mailto:[email protected]>> wrote:
Upgrade U-Boot to the latest version.
As usual, u-boot-mkimage broke again:
That's weird, I successfully built it for nios2 during my tests. Can you tell me how I can replicate the issue , so I can test for it to prevent regression and roll out a patch ?
Quoted 7 lines
Quoted 6 lines
Quoted 4 lines
Marek, Ross,
Any progress on this? Need any help testing?
Yeah, how do you replicate this issue ?
Hi!
Hi!
Quoted 7 lines
Quoted 4 lines
I am just looking at a similar problem and want to jump into the discussion. As Ross said, the problem is to not respect host/target -- cc/cflags/ldflags. So to replicate the issue, you can use a bare minimum build host with no cross toolchain installed, and I guess all targets will fail to build.
Well both ARM and nios2 builds for me, so I wonder what sort of stupid thing am I doing.
perhaps, its manifesting when toolchain is used from sstate, moreover the sstate comes from a mirror which is populated from a workspace which has different build time paths, which means its encoding a different default sysroot into toolchain. So unless you add TOOLCHAIN_OPTIONS to the CC and its ilk you will have issues.
May be you can reproduce it by
1. build first time ./oe-init-build-env /path/to/build1
2. Now set another builddir may be using ./oe-init-build-env /path/to/build2
3. Add a SSTATE_MIRROR pointing to sstate from first builddir add below to local.conf
SSTATE_MIRRORS ?= "\
file://.* file:///path/to/build1/sstate-cache/PATH”
4. bitbake <package>
5. bitbake -ccleansstate <package>
6. bitbake package
Quoted 42 lines
Quoted 13 lines
As this has been broken so many times, I want to discuss some possible fixes:
In the top levelMakefilewe have:
HOSTCC = cc
HOSTCFLAGS = ...
The problem is, you cannot properly override those variables, as they get used a lot to do different things, e.g. intools/Makefilewe have (for cross tools target) HOSTCC = $(CC) and for HOSTCFLAGS we have appends for configuration. Thats why we have the current workaround with a squashed override. I see many possible solutions and would like to hear your opinion:
1. Make top levelMakefileHOST assignments conditional "?="
- easy
- will probably not be accepted upstreamWhy ?
Quoted 6 lines
2. add "override" to appends in sublevel Makefiles
- adds complexity/one level of override hierarchy
3. Don't use appends for those variables (like in the kernelMakefile), overrides in the recipe
- clean
- quite some rework in ubootCan you provide details ?
Quoted 7 lines
4. Hack around in the recipe with class overrides and exports
- quickfix, no patch required
- fails easily in the futureAny thoughts?
Stefan--
Best regards,
Marek Vasut
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 54 lines · Khem Raj
Quoted 33 lines · Marek Vasut
Quoted 19 lines · Stefan Müller-Klieser
Quoted 18 lines · Marek Vasut
Quoted 17 lines · Denys Dmytriyenko
Quoted 15 lines · Marek Vasut
On 10/21/2016 09:47 AM, Burton, Ross wrote:
Hi!
Quoted 7 lines
On 20 October 2016 at 14:35, Marek Vasut <[email protected] <mailto:[email protected]>> wrote:
Upgrade U-Boot to the latest version.
As usual, u-boot-mkimage broke again:
That's weird, I successfully built it for nios2 during my tests. Can you tell me how I can replicate the issue , so I can test for it to prevent regression and roll out a patch ?
Quoted 7 lines
Quoted 6 lines
Quoted 4 lines
Marek, Ross,
Any progress on this? Need any help testing?
Yeah, how do you replicate this issue ?
Hi!
Hi!
Quoted 7 lines
Quoted 4 lines
I am just looking at a similar problem and want to jump into the discussion. As Ross said, the problem is to not respect host/target -- cc/cflags/ldflags. So to replicate the issue, you can use a bare minimum build host with no cross toolchain installed, and I guess all targets will fail to build.
Well both ARM and nios2 builds for me, so I wonder what sort of stupid thing am I doing.
perhaps, its manifesting when toolchain is used from sstate, moreover the sstate comes from a mirror which is populated from a workspace which has different build time paths, which means its encoding a different default sysroot into toolchain. So unless you add
TOOLCHAIN_OPTIONSto the CC and its ilk you will have issues.May be you can reproduce it by
1. build first time ./oe-init-build-env /path/to/build1
2. Now set another builddir may be using ./oe-init-build-env /path/to/build2
3. Add aSSTATE_MIRRORpointing to sstate from first builddir add below to local.conf
Quoted 6 lines
SSTATE_MIRRORS?= "\
file://.* file:///path/to/build1/sstate-cache/PATH”4. bitbake <package>
5. bitbake -ccleansstate <package>
6. bitbake package
This seems pretty convoluted. If I understand Ross correctly, it might be easier to just try the build on centos?
Signature · 2 lines
Best regards, Marek Vasut