mirror/libbpf
1
0
Fork 0
mirror of https://github.com/netdata/libbpf.git synced 2026-09-07 12:07:20 +08:00
Code Issues Packages Projects Releases Wiki Activity
1,568 Commits 29 Branches 44 Tags
f3cc144922652406958f4c0656ab170ff0e0cbda
Commit Graph
11 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
Frantisek Sumsal c42bfcbf0e travis: build on ppc64le as well 2019-12-13 01:04:46 -08:00
Frantisek Sumsal b91f53ec5f travis: use travis_terminate instead of set {+,-}e combo 
Apart from that it looks a bit nicer, it also acts as a workaround for
https://travis-ci.community/t/exit-0-cannot-exit-successfully-on-arm/5731/4
 2019-11-14 13:49:21 -08:00
Frantisek Sumsal dd8f1bdd45 travis: bump the Ubuntu release to Bionic 
The main reason why this is necessary is that gcc 5.x on Xenial doesn't
support ASan on s390x. Bumping the release to Bionic with gcc 7.x allows
us to build libbpf on s390x with ASan without issues.
 2019-11-14 13:49:21 -08:00
Frantisek Sumsal 3720f31852 travis: add an s390x job 
Travis now supports IBM Z and IBM Power architectures, so let's enable
them in our CI as well.

As libbpf won't compile on ppc64le right now (with current CFLAGS), let
skip it until the issue is resolved, see discussion in
https://github.com/libbpf/libbpf/pull/98#issuecomment-553873098

See: https://blog.travis-ci.com/2019-11-12-multi-cpu-architecture-ibm-power-ibm-z
 2019-11-14 13:49:21 -08:00
Frantisek Sumsal d7a137510a coverity: explicitly use bash instead of sh 
On Ubuntu `/bin/sh` is a symlink to `/bin/dash`, which doesn't support
certain builtins used by the Coverity script (namely pushd/popd)
 2019-11-05 13:28:13 -08:00
Frantisek Sumsal 91e4f27dd7 travis: use sudo during the 'install' phase 2019-11-04 15:08:38 -08:00
Frantisek Sumsal 1339ef70a3 README: add Coverity badge 2019-11-01 23:22:57 -07:00
Frantisek Sumsal c204e3d610 travis: automate Coverity builds 2019-11-01 23:22:57 -07:00
Frantisek Sumsal 32d0a03332 README: add a LGTM badge 2019-10-29 15:45:36 -07:00
Frantisek Sumsal b923d0e3c6 lgtm: fix the extraction process 
As this project uses only Makefile, without any configuration step, and due to
a "non-standard" location of the source files, LGTM kept failing to find the
respective Makefile and build the sources. By tricking LGTM's build system
auto detection, that we use automake/configure, it correctly sets the source
dir, thus the compilation, extraction & analysis steps now work in the src/
subdirectory, as expected.
 2019-10-28 15:15:47 -07:00
Frantisek Sumsal 2a25957df6 travis: add an aarch64 Xenial job 2019-10-23 10:13:54 -07:00