dmnks left a comment (rpm-software-management/rpm#3982)
The issue is that the `/var/cfengine/lib` directory is not a standard rpath as
defined by the script. There's a hardcoded list of path prefixes that are
considered "standard" (also see this [Fedora
Change](https://fedoraproject.org/wiki/Changes/Broken_RPATH_will_fail_rpmbuild#Definition_of_a_broken_RPATH)
for more context) and `/var` isn't included. I'd guess it's because binaries
normally shouldn't go there.
Now, the reason this error didn't occur on RHEL-9 is that the script actually
didn't check for `DT_RUNPATH` (only for `DT_RPATH`), which was later fixed by
commit 6b21e736a3e47071b33ff7c34e5cfb5447997e18. The binary that's being
examined in your case seems to only have the latter (which is the default when
using `gcc -Wl,-rpath` on Fedora/RHEL nowadays, and can be disabled by also
passing `--disable-new-dtags` to the linker) and thus it simply didn't get
picked up by the script.
That said, if the packager insist on a special rpath (which might be this
case), then they're free to use the workaround as documented (which the linked
commits above seems to have implemented).
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3982#issuecomment-3376755498
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/3982/[email protected]>
_______________________________________________
Rpm-maint mailing list
[email protected]
https://lists.rpm.org/mailman/listinfo/rpm-maint
