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 17:06:25 +0100 [thread overview]
Message-ID: <20171213160625.GA22116@rei> (raw)
In-Reply-To: <20171213142526.tozen4rtmaerbkma@dell5510>
Hi!
> > 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.
> Versions are 4.8.4 for both. It's actually visible in the log:
>
> https://travis-ci.org/pevik-travis/ltp/jobs/315469429
> $ arm-linux-gnueabihf-gcc --version
> arm-linux-gnueabihf-gcc (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.1) 4.8.4
> Copyright (C) 2013 Free Software Foundation, Inc.
>
> https://travis-ci.org/pevik-travis/ltp/jobs/315469430
> $ aarch64-linux-gnu-gcc --version
> aarch64-linux-gnu-gcc (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.1) 4.8.4
>
> > 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.
> The reason why it's not fixed is that it's possible only with special repository
> ubuntu-toolchain-r-test, which is used for other jobs. AFAIK they don't provide arm
> toolchain, that's why I used standard trusty repository for ARM.
>
> So is that ok as it is?
I guess so.
It's a smoke test so we have to keep the number of build reasonably
small and having arm builds is agruably more important than all possible
gcc flavors. Moreover we still run gcc-4.9 and gcc-6 for 32bit builds
right?
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-12-13 16:06 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
2017-12-13 14:25 ` Petr Vorel
2017-12-13 16:06 ` Cyril Hrubis [this message]
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=20171213160625.GA22116@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