Author moreati
Recipients Alex.Willmer, Arfrever, Link Mauve, benjamin.peterson, doko, freakboy3742, georg.brandl, koobs, mancoast, martin.panter, moreati, pitrou, rbcollins
Date 2016-03-14.09:21:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CABv=ZQGY4t9m6LmC2_OKkzDso4vyDNVwP+g7qcaoCa6_2ejYgg@mail.gmail.com>
In-reply-to <1457917511.02.0.185151432192.issue22625@psf.upfronthosting.co.za>
Content
On 14 March 2016 at 01:05, Robert Collins <report@bugs.python.org> wrote:
> There are three platforms in play: target, host, build.
>
> Host is the platform where what you build should run on.
> build is the platform we are building on.
> target is the platform where the *output* of the build thing itself should run on. Baby steps though: lets assume target==host always.

To be 100% explicit: CPython doesn't need to worry about the third
one, the target platform. That only matters when the thing being
compiled, will itself cross-compile/process binaries at runtime e.g.
gcc, binutils. So if

 - I'm on Linux and
 - I want to compile a gcc that runs on BeOS
 - that in turn compiles binaries for TempleOS

only then would target matter.
History
Date User Action Args
2016-03-14 09:21:28moreatisetrecipients: + moreati, georg.brandl, doko, pitrou, rbcollins, benjamin.peterson, Arfrever, freakboy3742, martin.panter, koobs, Alex.Willmer, Link Mauve, mancoast
2016-03-14 09:21:28moreatilinkissue22625 messages
2016-03-14 09:21:27moreaticreate