From: Ian Jackson <ian.jackson@citrix.com>
To: Julien Grall <julien.grall@arm.com>
Cc: Artem_Mygaiev@epam.com, Lars Kurth <lars.kurth@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
stefanos@xilinx.com, George Dunlap <dunlapg@umich.edu>,
xen-devel@lists.xenproject.org,
Stefano Stabellini <stefano.stabellini@xilinx.com>,
infra@xenproject.org
Subject: Re: [OSSTEST PATCH] README.hardware-acquisition [and 1 more messages] [and 2 more messages] [and 2 more messages]
Date: Fri, 2 Nov 2018 16:40:14 +0000 [thread overview]
Message-ID: <23516.32238.227539.570131@mariner.uk.xensource.com> (raw)
In-Reply-To: <c2d91264-2a06-cad1-c7f4-b0604b6ff80a@arm.com>
Julien Grall writes ("Re: [OSSTEST PATCH] README.hardware-acquisition [and 1 more messages] [and 2 more messages] [and 2 more messages]"):
> On 02/11/2018 15:44, Ian Jackson wrote:
> > We have more x86 capacity and are deploying some dedicated build
> > hosts. But cross-compilation is more complex (particularly the
> > compiler conflict...)
>
> Do you mean the multilib problem? This issue is only when cross-compiling tools
> (which I would not recommend anyway...). For things like kernel and hypervisor,
> you don't need multilib.
Yes, that problem.
I think by `cross-compiling' here you mean to include running gcc -m32
on an amd64 host or vice versa, which is not quite real
cross-compiling in my view. But it does require gcc-multilib.
But, as it turns out, you are right that this is not a problem for
osstest. When osstest does builds for an i386 dom0, it does the
hypervisor build on an amd64 host and the tools build separately on an
i386 host.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-11-02 16:40 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 16:13 [OSSTEST PATCH] README.hardware-acquisition Ian Jackson
2018-10-30 16:27 ` Jan Beulich
2018-10-30 20:28 ` Julien Grall
2018-10-30 22:38 ` Stefano Stabellini
2018-10-31 15:39 ` [OSSTEST PATCH] README.hardware-acquisition [and 1 more messages] Ian Jackson
2018-10-31 18:37 ` Stefano Stabellini
2018-11-01 12:42 ` [OSSTEST PATCH] README.hardware-acquisition [and 1 more messages] [and 2 " Ian Jackson
2018-11-01 18:12 ` Stefano Stabellini
2018-11-02 10:16 ` Lars Kurth
2018-11-02 14:16 ` Wei Liu
2018-11-02 16:19 ` Stefano Stabellini
2019-02-15 11:56 ` [OSSTEST PATCH] README.hardware-acquisition [and 1 " Ian Jackson
2019-02-15 12:15 ` Juergen Gross
2019-02-15 13:47 ` Lars Kurth
2019-02-15 15:40 ` Ian Jackson
2019-02-15 16:04 ` Lars Kurth
2019-02-15 17:07 ` Ian Jackson
2018-10-31 14:44 ` [OSSTEST PATCH] README.hardware-acquisition Ian Jackson
2018-10-31 18:32 ` Julien Grall
2018-10-31 17:49 ` George Dunlap
2018-10-31 17:50 ` George Dunlap
2018-10-31 18:46 ` Stefano Stabellini
2018-11-01 11:29 ` George Dunlap
2018-11-01 11:49 ` Lars Kurth
2018-11-01 17:50 ` Stefano Stabellini
2018-11-02 11:37 ` Ian Jackson
2018-11-02 15:05 ` [OSSTEST PATCH] README.hardware-acquisition [and 1 more messages] [and 2 more messages] [and 2 more messages] Ian Jackson
2018-11-02 15:38 ` Julien Grall
2018-11-02 15:44 ` Ian Jackson
2018-11-02 16:10 ` Julien Grall
2018-11-02 16:40 ` Ian Jackson [this message]
2018-11-02 17:56 ` Stefano Stabellini
2018-11-02 18:08 ` Julien Grall
2018-11-02 23:44 ` Stefano Stabellini
2018-11-05 11:08 ` Julien Grall
2018-11-05 11:32 ` Ian Jackson
2018-11-09 19:48 ` Stefano Stabellini
2018-11-05 10:55 ` Ian Jackson
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=23516.32238.227539.570131@mariner.uk.xensource.com \
--to=ian.jackson@citrix.com \
--cc=Artem_Mygaiev@epam.com \
--cc=dunlapg@umich.edu \
--cc=infra@xenproject.org \
--cc=julien.grall@arm.com \
--cc=lars.kurth@citrix.com \
--cc=sstabellini@kernel.org \
--cc=stefano.stabellini@xilinx.com \
--cc=stefanos@xilinx.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.