From: Wei Liu <wei.liu2@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Juergen Gross <JGross@suse.com>,
xuquan8@huawei.com, Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>,
samuel.thibault@ens-lyon.org, dgdegra@tycho.nsa.gov
Subject: Re: [PATCH for-4.8] stubdom: make GMP aware that it's being cross-compiled
Date: Mon, 31 Oct 2016 10:14:43 +0000 [thread overview]
Message-ID: <20161031101443.GO30231@citrix.com> (raw)
In-Reply-To: <581715A2020000780011AEF7@prv-mh.provo.novell.com>
On Mon, Oct 31, 2016 at 02:57:54AM -0600, Jan Beulich wrote:
> >>> On 29.10.16 at 19:22, <wei.liu2@citrix.com> wrote:
> > Append --build and --host flags to GMP's configure script so that it
> > knows it is being compiled for another architecture.
>
> Why --host and --build? Aiui,
> - host is where the configure runs,
> - build is where tool chain components being built are supposed to run,
> - target is where the final binaries are intended to run.
I think you got them wrong, in particular host and build semantics.
build is where the build runs, host is where the resulting binary runs,
target is where the output of the resulting binary runs (assuming the
binary is compiler).
https://www.gnu.org/software/autoconf/manual/autoconf-2.65/html_node/Specifying-Target-Triplets.html
Since GMP is not a compiler, target is not relevant here.
>
> We're talking about a simple cross build here afaict, not a Canadian
> cross,
Correct, it's a simple cross build, not a Canadian cross.
The rest is moot because it is based on wrong assumption.
Wei.
> i.e. host == build, with only target being different, i.e. I'd
> assume you really want to specify --target (and leave host and build
> to be determined automatically), along the lines of e.g. a simple
> compiler cross build, which produces
>
> S["target_os"]="linux-gnu"
> S["target_vendor"]="pc"
> S["target_cpu"]="x86_64"
> S["target"]="x86_64-pc-linux-gnu"
>
> S["host_os"]="linux-gnu"
> S["host_vendor"]="pc"
> S["host_cpu"]="i686"
> S["host"]="i686-pc-linux-gnu"
>
> S["build_os"]="linux-gnu"
> S["build_vendor"]="pc"
> S["build_cpu"]="i686"
> S["build"]="i686-pc-linux-gnu"
>
> among its awk expression to perform substitution in various other
> files/scripts (except that in the stubdom case it would be target_os
> to be different from host_os/build_os, and - on a 64-bit system -
> target_cpu matching host_cpu/build_cpu).
>
> Jan
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-10-31 10:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 17:22 [PATCH for-4.8] stubdom: make GMP aware that it's being cross-compiled Wei Liu
2016-10-31 8:57 ` Jan Beulich
2016-10-31 10:14 ` Wei Liu [this message]
2016-10-31 10:50 ` Jan Beulich
2016-10-31 11:45 ` Ian Jackson
2016-10-31 9:05 ` Juergen Gross
2016-10-31 10:21 ` Ian Jackson
2016-10-31 10:22 ` Samuel Thibault
2016-10-31 10:55 ` 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=20161031101443.GO30231@citrix.com \
--to=wei.liu2@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=JGross@suse.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=samuel.thibault@ens-lyon.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xuquan8@huawei.com \
/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.