rpms/valgrind
5
0
Fork 0
Code Issues Pull Requests Releases Activity

Update rpminspect.yaml for lto and valgrind-tools-devel

Browse Source 
Some extra excludes from Jesus Checa Hidalgo <jchecahi@redhat.com>
This commit is contained in:
Mark Wielaard 2021-11-19 14:24:49 +01:00
parent e2e1c0b1bf
commit b9b4facde8
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
rpminspect.yaml
View File

@ -5,6 +5,12 @@ inspections:
xml: off xml: off
annocheck: annocheck:
# Currently lto is disabled globally for valgrind, it should be able
# to be enabled through upstream configure --enable-lto in the future.
# Note that all (default fedora) flags need to be repeated here, if
# you override some config flags it will completely overwrite the
# defaults (--ignore-unknown --verbose).
- hardened: --ignore-unknown --verbose --skip-lto
# Ignore files built specially without hardening flags # Ignore files built specially without hardening flags
ignore: ignore:
# Valgrind tools themselves (memcheck, cachegrind, massif, etc) are # Valgrind tools themselves (memcheck, cachegrind, massif, etc) are
@ -24,6 +30,10 @@ annocheck:
# dependency on openmpi however, so a user can use the wrapper without # dependency on openmpi however, so a user can use the wrapper without
# explicitly pulling in openmpi unless the program explicitly uses it. # explicitly pulling in openmpi unless the program explicitly uses it.
- /usr/lib*/openmpi/valgrind/libmpiwrap-*-linux.so - /usr/lib*/openmpi/valgrind/libmpiwrap-*-linux.so
# These static archives (to create custom valgrind tools) are only
# distributed in valgrind-tools-devel and don't have hardening flags
# for the same reason as the standard tools (see above).
- /usr/lib*/valgrind/*-*linux.a
runpath: runpath:
allowed_paths: allowed_paths: