[LTP] [PATCH v2 1/2] travis: use various gcc and clang versions + using containers

[LTP] [PATCH v2 1/2] travis: use various gcc and clang versions + using containers

[Petr Vorel]

Using containers is declared to be faster, but does not allow us to use
sudo => install into $HOME.

Signed-off-by: Petr Vorel <pvorel@suse.cz>
---
Used gcc: 4.6, 4.7, 4.8. 4.9, 5, 6
Used clang: 3.5, 3.8, 3.9

I simplified patch. This way we cannot install clang-3.3, but I suppose it's ok.
Which versions are you interested? We can have even more versions, but even this subset is IMHO quite a lot.

Whole check takes about 12 min, see https://travis-ci.org/pevik-travis/ltp/builds/191565390
---
 .travis.yml | 72 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++---
 1 file changed, 69 insertions(+), 3 deletions(-)

diff --git a/.travis.yml b/.travis.yml
index 16c0cd477..86b96d630 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -1,9 +1,75 @@
-sudo: required
-
 language: c
 
+matrix:
+    include:
+        - os: linux
+          compiler: gcc-4.6
+          addons:
+              apt:
+                  sources: ['ubuntu-toolchain-r-test']
+                  packages: ['gcc-4.6']
+
+        - os: linux
+          compiler: gcc-4.7
+          addons:
+              apt:
+                  sources: ['ubuntu-toolchain-r-test']
+                  packages: ['gcc-4.7']
+
+        - os: linux
+          compiler: gcc-4.8
+          addons:
+              apt:
+                  sources: ['ubuntu-toolchain-r-test']
+                  packages: ['gcc-4.8']
+
+        - os: linux
+          compiler: gcc-4.9
+          addons:
+              apt:
+                  sources: ['ubuntu-toolchain-r-test']
+                  packages: ['gcc-4.9']
+
+        - os: linux
+          compiler: gcc-5
+          addons:
+              apt:
+                  sources: ['ubuntu-toolchain-r-test']
+                  packages: ['gcc-5']
+
+        - os: linux
+          compiler: gcc-6
+          addons:
+              apt:
+                  sources: ['ubuntu-toolchain-r-test']
+                  packages: ['gcc-6']
+
+        - os: linux
+          compiler: clang-3.5
+          addons:
+              apt:
+                  sources: ['ubuntu-toolchain-r-test', 'llvm-toolchain-precise-3.5']
+                  packages: ['clang-3.5']
+
+        - os: linux
+          compiler: clang-3.8
+          addons:
+              apt:
+                  sources: ['ubuntu-toolchain-r-test', 'llvm-toolchain-precise-3.8']
+                  packages: ['clang-3.8']
+
+        - os: linux
+          compiler: clang-3.9
+          addons:
+              apt:
+                  sources:
+                      - sourceline: "deb http://apt.llvm.org/trusty/ llvm-toolchain-trusty-3.9 main"
+                        key_url: "http://apt.llvm.org/llvm-snapshot.gpg.key"
+                      - 'ubuntu-toolchain-r-test'
+                  packages: ['clang-3.9']
+
 notifications:
     email:
         - ltp@lists.linux.it
 
-script: make autotools && ./configure --with-open-posix-testsuite --with-realtime-testsuite && make -j$(getconf _NPROCESSORS_ONLN) && make -j$(getconf _NPROCESSORS_ONLN) install
+script: make autotools && ./configure --prefix $HOME/ltp --with-open-posix-testsuite --with-realtime-testsuite && make -j$(getconf _NPROCESSORS_ONLN) && make -j$(getconf _NPROCESSORS_ONLN) install
-- 
2.11.0

[LTP] [PATCH v2 2/2] make: print compiler version

[Petr Vorel]

Signed-off-by: Petr Vorel <pvorel@suse.cz>
---
I thought it might be useful for non-travis builds to see from logs compiler
version.
---
 Makefile | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Makefile b/Makefile
index 94f2532fd..229f29d81 100644
--- a/Makefile
+++ b/Makefile
@@ -173,6 +173,7 @@ SRCDIR_INSTALL_TARGETS	:= $(SRCDIR_INSTALL_SCRIPTS) $(SRCDIR_INSTALL_READONLY)
 #
 .PHONY: Version
 Version:
+	$(CC) --version
 	if git describe >/dev/null 2>&1; then \
 		git describe > "$@"; \
 	else \
-- 
2.11.0

[LTP] [PATCH v2 1/2] travis: use various gcc and clang versions + using containers

[Cyril Hrubis]

Hi!
> Using containers is declared to be faster, but does not allow us to use
> sudo => install into $HOME.
> 
> Signed-off-by: Petr Vorel <pvorel@suse.cz>

Applied thanks.

> ---
> Used gcc: 4.6, 4.7, 4.8. 4.9, 5, 6
> Used clang: 3.5, 3.8, 3.9
> 
> I simplified patch. This way we cannot install clang-3.3, but I suppose it's ok.
> Which versions are you interested? We can have even more versions, but even this subset is IMHO quite a lot.

I guess that we cover more than enough compiler versions now.

What I would be intersted in in the long term would be running LTP build
on some sligthly older distribution (debian stable or oldstable should
be quite easy with debootstrap) as well as do a 32bit build [1]. So
maybe we can omit build for some gcc versions and rather work on these
two options.

[1]
https://github.com/patricksnape/test-travis-chroot-32/blob/master/setup_travis.sh

-- 
Cyril Hrubis
chrubis@suse.cz

[LTP] [PATCH v2 2/2] make: print compiler version

[Cyril Hrubis]

Hi!
> I thought it might be useful for non-travis builds to see from logs compiler
> version.

I'm not against this, but priting it as a first line after make does not
feel right. Maybe we can print some summary (compiler version, enabled
devel libraries) at the end of the configure script. But I do not think
that this will be useful enough to spend significant amout of time on
it.

-- 
Cyril Hrubis
chrubis@suse.cz

[LTP] [PATCH v2 1/2] travis: use various gcc and clang versions + using containers

[Petr Vorel]

Hi!

> Applied thanks.
Thanks :-).

> What I would be intersted in in the long term would be running LTP build
> on some sligthly older distribution (debian stable or oldstable should
> be quite easy with debootstrap) as well as do a 32bit build [1]. So
> maybe we can omit build for some gcc versions and rather work on these
> two options.
I thought that old gcc and clang versions would emulate older distros (currently defined compilers have similar versions to gcc for Debian from oldstable to unstable, Ubuntu from precise zesty and to clang from Debian stable to unstable and xenial to zesty).
But true, at least 32bit and cross compilation wouldn't be solved by it.

> [1]
> https://github.com/patricksnape/test-travis-chroot-32/blob/master/setup_travis.sh
Looks interesting, I'll test it in near future. It uses sudo, which is declared to be
slower, but it looks the same to me.


Kind regards,
Petr

[LTP] [PATCH v2 1/2] travis: use various gcc and clang versions + using containers

[Cyril Hrubis]

Hi!
> > What I would be intersted in in the long term would be running LTP build
> > on some sligthly older distribution (debian stable or oldstable should
> > be quite easy with debootstrap) as well as do a 32bit build [1]. So
> > maybe we can omit build for some gcc versions and rather work on these
> > two options.
>
> I thought that old gcc and clang versions would emulate older distros
> (currently defined compilers have similar versions to gcc for Debian
> from oldstable to unstable, Ubuntu from precise zesty and to clang
> from Debian stable to unstable and xenial to zesty).  But true, at
> least 32bit and cross compilation wouldn't be solved by it.

That is not 100% true. We would have to install older libc-devel as
well. If we could do that it would be much easier than setting up
debootstrap chroot.

-- 
Cyril Hrubis
chrubis@suse.cz