From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] travis.yml: change Ubuntu version to xenial
Date: Mon, 12 Aug 2019 12:41:49 -0400 [thread overview]
Message-ID: <20190812164149.GU2718@bill-the-cat> (raw)
In-Reply-To: <11067CAC-9942-45A4-B3B9-98918C4C6FD8@gmail.com>
On Wed, Jul 17, 2019 at 08:24:18PM +0300, Ramon Fried wrote:
>
>
> On July 17, 2019 7:42:30 PM GMT+03:00, Tom Rini <trini@konsulko.com> wrote:
> >On Wed, Jul 17, 2019 at 07:37:23PM +0300, Ramon Fried wrote:
> >>
> >>
> >> On July 17, 2019 4:29:04 PM GMT+03:00, Tom Rini <trini@konsulko.com>
> >wrote:
> >> >On Mon, Jul 15, 2019 at 03:26:27AM +0300, Ramon Fried wrote:
> >> >
> >> >> trusty is getting old, move to xenial (16.04)
> >> >> to get updated gcc and other tools.
> >> >>
> >> >> Signed-off-by: Ramon Fried <rfried.dev@gmail.com>
> >> >> ---
> >> >> .travis.yml | 2 +-
> >> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >> >>
> >> >> diff --git a/.travis.yml b/.travis.yml
> >> >> index c21bbbbca4..1640fbb6dd 100644
> >> >> --- a/.travis.yml
> >> >> +++ b/.travis.yml
> >> >> @@ -4,7 +4,7 @@
> >> >> # build U-Boot on Travis CI - https://travis-ci.org/
> >> >>
> >> >> sudo: required
> >> >> -dist: trusty
> >> >> +dist: xenial
> >> >>
> >> >> language: c
> >> >>
> >> >
> >> >Oh good, they're finally not stuck on "Trusty". But I still think
> >we
> >> >need to move to GitLab CI runners instead, so we can have better
> >> >control
> >> >over (and provide resources for) running the builds instead.
> >> This can be an intermediate state until movement to gitlab CI is
> >complete.
> >> Thanks, Ramon
> >
> >What's the case where things aren't working, today, that xenial fixes?
> >And please note that the GitLab CI move is underway (I posted
> >translating .travis.yml to .gitlab-ci.yml a while ago, now that the
> >merge window is open I need to apply it, the current new travis stuff,
> >and update it again).
> host compilation with a more recent gcc compiler (5.4). instead of (4.8).
> newer supporting packages.
One other concern I have here (so please v2) is that we aren't updating
the section to grab a "xenial" LLVM toolchain, just trusty still.
Thanks!
--
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/20190812/76ec2322/attachment.sig>
next prev parent reply other threads:[~2019-08-12 16:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 0:26 [U-Boot] [PATCH] travis.yml: change Ubuntu version to xenial Ramon Fried
2019-07-15 1:48 ` Bin Meng
2019-07-15 4:44 ` Ramon Fried
2019-07-15 7:05 ` Ramon Fried
2019-07-17 13:29 ` Tom Rini
2019-07-17 16:37 ` Ramon Fried
2019-07-17 16:42 ` Tom Rini
2019-07-17 17:24 ` Ramon Fried
2019-08-12 16:41 ` Tom Rini [this message]
2019-08-12 16:53 ` Ramon Fried
2019-08-12 16:55 ` Tom Rini
2019-08-12 17:44 ` Ramon Fried
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=20190812164149.GU2718@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