From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] travis: Add sandbox/clang-7 support
Date: Tue, 9 Oct 2018 07:35:11 -0400 [thread overview]
Message-ID: <20181009113511.GK5539@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ2MrvFkDSkjB1FGVUjmpB=swDuY7utfmXEUH5Cs6+CPjg@mail.gmail.com>
On Mon, Oct 08, 2018 at 09:40:51PM -0600, Simon Glass wrote:
> Hi Tom,
>
> On 7 October 2018 at 12:20, Tom Rini <trini@konsulko.com> wrote:
> >
> > To make testing with clang support easier, add sandbox/clang-7
> > combination to our testing matrix. To facilitate this, switch to using
> > the "sources" method that the travis.yml file supports to list
> > additional repositories and add the official one for llvm-7. Due to
> > buildman not supporting using clang at this time add logic to manually
> > build a single sandbox configuration in the expected output directory so
> > that we can still invoke all of our tests.
> >
> > Cc: Simon Glass <sjg@chromium.org>
> > Signed-off-by: Tom Rini <trini@konsulko.com>
> > ---
> > .travis.yml | 27 ++++++++++++++++++++-------
> > 1 file changed, 20 insertions(+), 7 deletions(-)
>
> Reviewed-by: Simon Glass <sjg@chromium.org>
>
> What prevents buildman supporting clang?
Well, I couldn't convince buildman to accept "/usr/bin/clang-7" as the
full and entire path to the toolchain to use. Ideas? 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/20181009/ce7779eb/attachment.sig>
next prev parent reply other threads:[~2018-10-09 11:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 18:20 [U-Boot] [PATCH] travis: Add sandbox/clang-7 support Tom Rini
2018-10-09 3:40 ` Simon Glass
2018-10-09 11:35 ` Tom Rini [this message]
2018-10-19 3:27 ` Simon Glass
2018-10-20 19:11 ` [U-Boot] " 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=20181009113511.GK5539@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