From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Olaf Hering <olaf@aepfle.de>, <xen-devel@lists.xenproject.org>
Cc: Ian Jackson <iwj@xenproject.org>, Wei Liu <wl@xen.org>
Subject: Re: [PATCH v1] tools: ipxe: update for fixing build with GCC11
Date: Wed, 16 Jun 2021 13:33:52 +0100 [thread overview]
Message-ID: <b78ccdf3-9898-c903-4d9f-4d25bd27182e@citrix.com> (raw)
In-Reply-To: <20210615212613.6270-1-olaf@aepfle.de>
On 15/06/2021 22:26, Olaf Hering wrote:
> Use a snapshot which includes commit
> f3f568e382a5f19824b3bfc6081cde39eee661e8 ("[crypto] Add
> memory output constraints for big-integer inline assembly"),
> which fixes build with gcc11.
>
> Signed-off-by: Olaf Hering <olaf@aepfle.de>
> ---
> tools/firmware/etherboot/Makefile | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tools/firmware/etherboot/Makefile b/tools/firmware/etherboot/Makefile
> index ed9e11305f..23b3f6ca9d 100644
> --- a/tools/firmware/etherboot/Makefile
> +++ b/tools/firmware/etherboot/Makefile
> @@ -10,7 +10,8 @@ else
> IPXE_GIT_URL ?= git://git.ipxe.org/ipxe.git
> endif
>
> -IPXE_GIT_TAG := 988d2c13cdf0f0b4140685af35ced70ac5b3283c
> +# put an updated tar.gz on xenbits after changes to this variable
> +IPXE_GIT_TAG := bf4ccd4265ac614fbfa38bf168b6eeaf4c17d51e
CI says no.
Gitlab CI is currently fairly red because of a clang build fix which
hasn't made its way into master yet, but this job:
https://gitlab.com/xen-project/patchew/xen/-/jobs/1349871230
shows a real failure on CentOS 7.
...
[VERSION] bin/version.rtl8139.rom.o
[AR] bin/blib.a
ar: creating bin/blib.a
objcopy: invalid option -- 'D'
Usage: objcopy [option(s)] in-file [out-file]
...
~Andrew
next prev parent reply other threads:[~2021-06-16 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 21:26 [PATCH v1] tools: ipxe: update for fixing build with GCC11 Olaf Hering
2021-06-16 12:33 ` Andrew Cooper [this message]
2021-06-16 12:58 ` Olaf Hering
2021-06-16 13:33 ` Bernhard M. Wiedemann
2021-06-17 12:55 ` Michael Brown
2021-06-17 13:47 ` Michael Brown
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=b78ccdf3-9898-c903-4d9f-4d25bd27182e@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=iwj@xenproject.org \
--cc=olaf@aepfle.de \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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;
as well as URLs for NNTP newsgroup(s).