From 174594865e80c589f4506c50a409ba06a9741b63 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Lenka=20=C5=A0pa=C4=8Dkov=C3=A1?= <lspackova@redhat.com>
Date: Tue, 6 May 2025 11:36:06 +0200
Subject: [PATCH] Add rpminspect.yaml

Resolves: RHEL-88090
---
 rpminspect.yaml | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 rpminspect.yaml

diff --git a/rpminspect.yaml b/rpminspect.yaml
new file mode 100644
index 0000000..cb39742
--- /dev/null
+++ b/rpminspect.yaml
@@ -0,0 +1,22 @@
+badfuncs:
+    # GCC doesn't use the "forbidden" functions as such. Just some of its
+    # sanitizers can instrument those functions which leads to false
+    # positives in the badfuncs test.
+    ignore:
+      - /usr/lib*/libasan.so.*.*.*
+      - /usr/lib*/libtsan.so.*.*.*
+
+specname:
+    # In GCC toolsets builds, the spec file name and the package are not
+    # exactly the same, the package is prefixed with gcc-toolset-NN-.
+    # Let's ignore the prefix.
+    match: suffix
+    primary: filename
+
+runpath:
+    # Although gcc-toolset sanitizers link gcc-toolset libraries from
+    # /opt/..., they themselves are placed in /usr. The runpath test
+    # doesn't like this difference. Explicitly allow it.
+    allowed_paths:
+      - /opt/rh/gcc-toolset-13/root/usr/lib64
+      - /opt/rh/gcc-toolset-13/root/usr/lib