From: Doug Goldstein <cardoe@cardoe.com>
To: Wei Liu <wei.liu2@citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH RFC 2/3] automation: build stubdom and rombios, and tools on 32 bit
Date: Tue, 29 May 2018 00:18:40 -0500 [thread overview]
Message-ID: <13b83460-a84b-0888-0261-2c7bb5085594@cardoe.com> (raw)
In-Reply-To: <20180523102040.16299-3-wei.liu2@citrix.com>
On 5/23/18 5:20 AM, Wei Liu wrote:
>
> # SeaBIOS cannot be built with clang
> @@ -20,12 +18,6 @@ if [[ "${CC}" == "clang" ]]; then
> cfgargs+=("--with-system-seabios=/usr/share/seabios/bios.bin")
> fi
>
> -if [[ "${XEN_TARGET_ARCH}" == "x86_64" ]]; then
> - cfgargs+=("--enable-tools")
> -else
> - cfgargs+=("--disable-tools") # we don't have the cross depends installed
> -fi
> -
This still horribly fails when targeting arm because we have to actually
execute a compiled binary on the host. The tools build system doesn't
seem to comprehend host != target.
A few people have stepped forward with ideas and said they'd take point
on the patches but I haven't seen anything land yet.
--
Doug Goldstein
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-05-29 5:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 10:20 [PATCH RFC 0/3] Improvements to docker-based build automation Wei Liu
2018-05-23 10:20 ` [PATCH RFC 1/3] automation: install texinfo in debian Wei Liu
2018-05-29 5:21 ` Doug Goldstein
2018-05-29 23:25 ` Wei Liu
2018-05-23 10:20 ` [PATCH RFC 2/3] automation: build stubdom and rombios, and tools on 32 bit Wei Liu
2018-05-29 5:18 ` Doug Goldstein [this message]
2018-05-29 23:28 ` Wei Liu
2018-07-06 18:52 ` Doug Goldstein
2018-07-06 22:28 ` Stefano Stabellini
2018-05-23 10:20 ` [PATCH RFC 3/3] automation: introduce stretch-i386.dockerfile Wei Liu
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=13b83460-a84b-0888-0261-2c7bb5085594@cardoe.com \
--to=cardoe@cardoe.com \
--cc=wei.liu2@citrix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.