Skip to contentSkip to conversation

U-Boot v2018.11-rc3 released

U-Boot Tom Rini 2 participants 3 messages Oct 29, 2018 – Oct 30, 2018

lore
Share & tools
lore

Tom Rini

author
#0 lore raw

Hey all,

It's two weeks until v2018.11 release and today I've put out rc3. The delta is pretty reasonable and at this point I can really hold things to either obviously correct fixes or bugfixes/regression fixes/Kconfig migrations that can be proven out.

Thanks all!

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20181029/26f3b3f9/attachment.sig>
#1 lore raw
Quoted 7 lines · Tom Rini

Hey all,

It's two weeks until v2018.11 release and today I've put out rc3. The delta is pretty reasonable and at this point I can really hold things to either obviously correct fixes or bugfixes/regression fixes/Kconfig migrations that can be proven out.

So I'm a bit behind this cycle in getting Fedora builds done. We do tools-all build across all Fedora architectures and this is now failing due to trying to build something around the sandbox, I'm not sure how best to deal with this, whether it's an unintended regression, or if there's a new tools-all-but-not-sandbox option I missed or something else. Suggestions?

Peter

gcc -E -Wall -Wstrict-prototypes -Wno-format-security -fno-builtin
-ffreestanding -std=gnu11 -fshort-wchar -fno-strict-aliasing -fno-PIE -O2 -fno-stack-protector -fno-delete-null-pointer-checks -fmacro-prefix-map=../= -g -fstack-usage -Wno-format-nonliteral
-Werror=date-time -D__KERNEL__ -D__UBOOT__ -D__SANDBOX__
-U_FORTIFY_SOURCE -DCONFIG_ARCH_MAP_SYSMEM -fPIC -pipe -Iinclude -I../include -I../arch/sandbox/include -include ../include/linux/kconfig.h -nostdinc -isystem /usr/lib/gcc/ppc64le-redhat-linux/8/include -DDO_DEPS_ONLY -dM ../include/common.h > u-boot.cfg.tmp && { grep 'define CONFIG_' u-boot.cfg.tmp > u-boot.cfg; rm u-boot.cfg.tmp; } || { rm u-boot.cfg.tmp; false; }
In file included from ../include/configs/sandbox.h:66,

                 from include/config.h:5,
                 from ../include/common.h:20:
../include/config_distro_bootcmd.h:279:3: error: #error "sandbox EFI
support is only supported on ARM and x86"
 # error "sandbox EFI support is only supported on ARM and x86"
   ^~~~~
In file included from ../include/configs/sandbox.h:66,
                 from include/config.h:5,
                 from ../include/common.h:20:
../include/config_distro_bootcmd.h:279:3: error: #error "sandbox EFI
support is only supported on ARM and x86"
 # error "sandbox EFI support is only supported on ARM and x86"
   ^~~~~
make[2]: *** [../scripts/Makefile.autoconf:48: include/autoconf.mk.dep] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [../scripts/Makefile.autoconf:77: u-boot.cfg] Error 1
make -f ../scripts/Makefile.build obj=scripts/basic
make[1]: *** No rule to make target 'include/config/auto.conf', needed
by 'include/config/uboot.release'.  Stop.
make[1]: *** Waiting for unfinished jobs....
rm -f .tmp_quiet_recordmcount
make[1]: Leaving directory '/builddir/build/BUILD/u-boot-2018.11-rc3/builds'
author
#2 lore raw
Quoted 31 lines · Peter Robinson
Quoted 7 lines · Tom Rini

Hey all,

It's two weeks until v2018.11 release and today I've put out rc3. The delta is pretty reasonable and at this point I can really hold things to either obviously correct fixes or bugfixes/regression fixes/Kconfig migrations that can be proven out.

So I'm a bit behind this cycle in getting Fedora builds done. We do tools-all build across all Fedora architectures and this is now failing due to trying to build something around the sandbox, I'm not sure how best to deal with this, whether it's an unintended regression, or if there's a new tools-all-but-not-sandbox option I missed or something else. Suggestions?

Peter

gcc -E -Wall -Wstrict-prototypes -Wno-format-security -fno-builtin

(quoted diff) +0 -6
-ffreestanding -std=gnu11 -fshort-wchar -fno-strict-aliasing -fno-PIE
-O2 -fno-stack-protector -fno-delete-null-pointer-checks
-fmacro-prefix-map=../= -g -fstack-usage -Wno-format-nonliteral
-Werror=date-time  -D__KERNEL__ -D__UBOOT__   -D__SANDBOX__
-U_FORTIFY_SOURCE -DCONFIG_ARCH_MAP_SYSMEM -fPIC  -pipe -Iinclude
-I../include -I../arch/sandbox/include -include

../include/linux/kconfig.h -nostdinc -isystem /usr/lib/gcc/ppc64le-redhat-linux/8/include -DDO_DEPS_ONLY -dM ../include/common.h > u-boot.cfg.tmp && { grep 'define CONFIG_' u-boot.cfg.tmp > u-boot.cfg; rm u-boot.cfg.tmp; } || { rm u-boot.cfg.tmp; false; }
In file included from ../include/configs/sandbox.h:66,

Quoted 5 lines
                 from include/config.h:5,
                 from ../include/common.h:20:
../include/config_distro_bootcmd.h:279:3: error: #error "sandbox EFI
support is only supported on ARM and x86"
 # error "sandbox EFI support is only supported on ARM and x86"

Oh fun, so, we don't have a Kconfig-way to determine what the host architecture is I gather. Maybe we can move that #error to another file perhaps?

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20181030/e87ef19a/attachment.sig>