From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 4/4] travis: Install all dependencies (headers and libraries)
Date: Wed, 29 Nov 2017 16:48:06 +0100 [thread overview]
Message-ID: <20171129154806.GE15160@rei> (raw)
In-Reply-To: <20171128232130.4843-5-pvorel@suse.cz>
Hi!
> before_install:
> + - sudo apt install -f -y
> + libacl1-dev
> + libacl1:amd64
> + libacl1:i386
> + libaio-dev
> + libaio1:amd64
> + libaio1:i386
> + libcap-dev
> + libcap2:amd64
> + libcap2:i386
> + libc6
> + libc6-dev
> + libc6-dev-i386
> + libc6:i386
> + libkeyutils-dev
> + libkeyutils1:amd64
> + libkeyutils1:i386
> + libmm-dev
> + libnuma-dev
> + libnuma1:amd64
> + libnuma1:i386
> + libselinux1-dev:amd64
> + libssl-dev:amd64
> + libssl-dev:i386
> + libsepol1-dev:amd64
> + libssl-dev
> + libtirpc1:amd64
> + libtirpc1:i386
> + linux-libc-dev
This runs before each compilation, right? Can we have one build
just with the basic C devel packages as well, since that have found
most bugs in stubs and fallback code so far.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-11-29 15:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 23:21 [LTP] [RFC PATCH 0/4] Travis enhancements Petr Vorel
2017-11-28 23:21 ` [LTP] [RFC PATCH 1/4] travis: Add build script Petr Vorel
2017-11-29 8:13 ` Li Wang
2017-11-29 8:27 ` Petr Vorel
2017-11-29 8:41 ` Li Wang
2017-11-29 14:52 ` Petr Vorel
2017-11-29 15:42 ` Cyril Hrubis
2017-11-29 18:31 ` Petr Vorel
2017-11-30 2:09 ` Li Wang
2017-11-28 23:21 ` [LTP] [RFC PATCH 2/4] travis: Add 32 cross-compile build + use build.sh Petr Vorel
2017-11-29 15:45 ` Cyril Hrubis
2017-11-28 23:21 ` [LTP] [RFC PATCH 3/4] travis: Add gcc-7, clang-4.0, clang-5.0, remove clang-3.9 Petr Vorel
2017-11-28 23:21 ` [LTP] [RFC PATCH 4/4] travis: Install all dependencies (headers and libraries) Petr Vorel
2017-11-29 15:48 ` Cyril Hrubis [this message]
2017-11-29 18:59 ` Petr Vorel
2017-11-29 15:44 ` [LTP] [RFC PATCH 0/4] Travis enhancements Cyril Hrubis
2017-11-29 19:07 ` 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=20171129154806.GE15160@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.