From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 2/2] travis: Add 2x cross-compile ARM build
Date: Wed, 13 Dec 2017 14:58:08 +0100 [thread overview]
Message-ID: <20171213135808.GE11493@rei> (raw)
In-Reply-To: <20171212174544.12310-3-pvorel@suse.cz>
Hi!
> Builds replace native gcc-4.9 and gcc-6 builds to keep max 10 build
> jobs in travis.
So the cross compilers are gcc-4.x and gcc-6.x? I ask since we just ask
for arm cross compilers without a version in the script below.
I that is true I suppose that the cross compiler versions may change
without us noticing, which is not that big deal but it may be better to
select specific version instead if possible.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-12-13 13:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 17:45 [LTP] [RFC PATCH 0/2] travis: Cross-compile ARM builds Petr Vorel
2017-12-12 17:45 ` [LTP] [RFC PATCH 1/2] build.sh: Add cross-compile build option Petr Vorel
2017-12-12 17:45 ` [LTP] [RFC PATCH 2/2] travis: Add 2x cross-compile ARM build Petr Vorel
2017-12-13 13:58 ` Cyril Hrubis [this message]
2017-12-13 14:25 ` Petr Vorel
2017-12-13 16:06 ` Cyril Hrubis
2017-12-14 19:04 ` Petr Vorel
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=20171213135808.GE11493@rei \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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