From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] travis: Switch to i386 version toolchain for x86
Date: Mon, 8 Oct 2018 22:49:24 -0400 [thread overview]
Message-ID: <20181009024924.GJ5539@bill-the-cat> (raw)
In-Reply-To: <CAEUhbmU3Sk0OFx386wkky+2vjoQD-E3EJA3ogirGG+1Ge3XoZQ@mail.gmail.com>
On Tue, Oct 09, 2018 at 09:21:05AM +0800, Bin Meng wrote:
> Hi Tom,
>
> On Tue, Oct 9, 2018 at 7:53 AM Tom Rini <trini@konsulko.com> wrote:
> >
> > On Mon, Oct 08, 2018 at 04:53:54PM -0700, Bin Meng wrote:
> >
> > > Currently this uses x86_64 version toolchain for x86 build in
> > > travis-ci. Change it to i386 version to avoid updating the
> > > buildman toolchain path every time when the toolchain version
> > > number is changed, eg: from 7.3.0 to 8.1.0.
> > >
> > > Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
> >
> > I'm surprised this is fine, doesn't it break 64bit x86 targets?
>
> No, in fact I have always been using the i386 toolchain to test
> qemu-x86_64 target on my local machine. U-Boot x86 makefile fragments
> have been toolchain agnostic for some time.
Ah, OK, thanks. Yes, this will make upgrades easier too.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20181008/457c97ad/attachment.sig>
next prev parent reply other threads:[~2018-10-09 2:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 23:53 [U-Boot] [PATCH 1/2] travis: Remove or32 toolchain info Bin Meng
2018-10-08 23:53 ` [U-Boot] [PATCH 2/2] travis: Switch to i386 version toolchain for x86 Bin Meng
2018-10-08 23:53 ` Tom Rini
2018-10-09 1:21 ` Bin Meng
2018-10-09 2:49 ` Tom Rini [this message]
2018-10-20 19:11 ` [U-Boot] [U-Boot, " Tom Rini
2018-10-20 19:11 ` [U-Boot] [U-Boot,1/2] travis: Remove or32 toolchain info Tom Rini
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=20181009024924.GJ5539@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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