From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 1/2] travis: use various gcc and clang versions + using containers
Date: Mon, 16 Jan 2017 15:04:48 +0100 [thread overview]
Message-ID: <20170116140448.GD26610@rei.lan> (raw)
In-Reply-To: <20170116135444.hrpikajps735uhmk@dell5510>
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
prev parent reply other threads:[~2017-01-16 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 9:07 [LTP] [PATCH v2 1/2] travis: use various gcc and clang versions + using containers Petr Vorel
2017-01-13 9:07 ` [LTP] [PATCH v2 2/2] make: print compiler version Petr Vorel
2017-01-16 10:27 ` Cyril Hrubis
2017-01-16 10:25 ` [LTP] [PATCH v2 1/2] travis: use various gcc and clang versions + using containers Cyril Hrubis
2017-01-16 13:54 ` Petr Vorel
2017-01-16 14:04 ` Cyril Hrubis [this message]
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=20170116140448.GD26610@rei.lan \
--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