From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2018.11-rc3 released
Date: Tue, 30 Oct 2018 13:07:45 -0400 [thread overview]
Message-ID: <20181030170745.GU1032@bill-the-cat> (raw)
In-Reply-To: <CALeDE9MFqBW=SVx7F+ZZmiDCqTy5Zh5vx0kxqF8vyEdwAiq+tQ@mail.gmail.com>
On Tue, Oct 30, 2018 at 04:19:35PM +0000, Peter Robinson wrote:
> On Mon, Oct 29, 2018 at 8:05 PM Tom Rini <trini@konsulko.com> wrote:
> >
> > 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"
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?
--
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>
prev parent reply other threads:[~2018-10-30 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 20:05 [U-Boot] [ANN] U-Boot v2018.11-rc3 released Tom Rini
2018-10-30 16:19 ` Peter Robinson
2018-10-30 17:07 ` Tom Rini [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181030170745.GU1032@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox