From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 1/1] doc: Add supported kernel, libc versions
Date: Mon, 17 May 2021 08:50:54 +0200 [thread overview]
Message-ID: <YKISTkJGjp4blNH+@pevik> (raw)
In-Reply-To: <60A2040A.4080002@fujitsu.com>
Hi all,
> Hi Petr
> > Signed-off-by: Petr Vorel<pvorel@suse.cz>
> > ---
> > doc/supported-kernel-libc-versions.txt | 57 ++++++++++++++++++++++++++
> > 1 file changed, 57 insertions(+)
> > create mode 100644 doc/supported-kernel-libc-versions.txt
> > diff --git a/doc/supported-kernel-libc-versions.txt b/doc/supported-kernel-libc-versions.txt
> > new file mode 100644
> > index 000000000..b7ae01f11
> > --- /dev/null
> > +++ b/doc/supported-kernel-libc-versions.txt
> > @@ -0,0 +1,57 @@
> > +Supported kernel, libc, toolchain versions
> > +==========================================
> > +
> > +1. Build testing with Travis CI
> > +-------------------------------
> > +
> > +We test master branch in https://travis-ci.org/github/linux-test-project/ltp/builds[travis CI]
> > +to ensure LTP builds on various distributions including old, current and bleeding edge.
> > +We test both gcc and clang toolchains, various arch with cross-compilation.
> > +
> > +For list of tested distros see
> > +https://github.com/linux-test-project/ltp/blob/master/.travis.yml[.travis.yml].
> > +
> > +
> > +NOTE: Travis does only build testing, passing the CI means only that the
> > + test compiles fine on variety of different distributions and releases.
> AFAIK, travis uses lastest distribution image to build. So it may exist
> the situation that it build pass on lastest centos7 and build failed on
> older centos7. I think we should add a note in here.
+1
> > +
> > +1.1 Oldest tested distributions
> > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > +
> > +[align="center",options="header"]
> > +|==============================================================
> > +| Distro | kernel | glibc | gcc | clang
> > +| CentOS 7 | 3.10 | 2.17 | 4.8.5 | -
> > +| Ubuntu 16.04 LTS xenial | 4.4 | 2.23 | 5.3.1 | -
> > +| Debian 9 stretch (oldstable) | 4.9.30 | 2.24 | 6.3.0 | 3.8
> > +|==============================================================
This means we need to update time to time, at least for CentOS and Debian.
Debian moves to another release after current testing gets released.
We might want to use names (e.g. stretch) instead of "oldstable", "stable".
(I slightly prefer current approach, but not having a strong opinion)
> > +
> > +For older versions please use https://github.com/linux-test-project/ltp/releases[older LTP releases].
> > +
> > +1.2 Supported architectures
> > +~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > +
> > +[align="center",options="header"]
> > +|==================================
> > +| arch | build
> > +| x86_64 | native
> > +| x86 emulation | native
> > +| aarch64 | cross compilation
> > +| ppc64le | cross compilation
> > +| s390x | cross compilation
> > +|==================================
nit: not sure if having this as a table and supported libc (next section) just
paragraphs.
> > +
> > +1.3 Supported libc
> > +~~~~~~~~~~~~~~~~~~
> > +
> > +Targeted libc is https://www.gnu.org/software/libc/[GNU C Library (glibc)].
> > +
> > +https://uclibc-ng.org/[uClibc-ng] is not being tested should work as well as it
> > +attempt to maintain a glibc compatible interface
> > +(older https://www.uclibc.org/[uClibc] might have problems).
> > +
> > +https://musl.libc.org/[musl] is not yet supported
> > +(see https://github.com/linux-test-project/ltp/blob/master/travis/alpine.sh[travis script]
> > +for list of files which need to be deleted in order to compile under musl).
> > +
> > +For bionic libc please (Android) use https://android.googlesource.com/platform/external/ltp/[AOSP fork].
Kind regards,
Petr
prev parent reply other threads:[~2021-05-17 6:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 13:26 [LTP] [RFC PATCH 1/1] doc: Add supported kernel, libc versions Petr Vorel
2021-05-14 13:53 ` Cyril Hrubis
2021-05-14 15:06 ` [LTP] [Automated-testing] " Petr Vorel
2021-05-17 13:56 ` Cyril Hrubis
2021-05-18 8:29 ` Li Wang
2021-05-17 5:55 ` [LTP] " Jan Stancek
2021-05-17 6:42 ` Petr Vorel
2021-05-17 5:49 ` xuyang2018.jy
2021-05-17 6:50 ` Petr Vorel [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=YKISTkJGjp4blNH+@pevik \
--to=pvorel@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