Like others have pointed out, this is not a feasible approach. Private
dependencies of other projects are just that: private, and we have no business
(or interest) guessing what they might be for any given project. As already
pointed out, the constructive path forward is to to get libmagic to
Closed #118.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/118#event-915750694___
Rpm-maint mailing list
The correct change is to get the file/libmagic project to ship a file for
pkg-config to use and stop relying on creaky manual tests.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Are you going to submit patches like this to every project that uses -lmagic?
Are you going to list every library libmagic might happen to be linked with?
No, -lmagic users should not care about the list of libraries libmagic is
linked with, sorry.
--
You are receiving this because you are
When attempting to check for `magic_open` in libmagic (aka file),
linking can fail as libmagic and zlib may have been statically built:
configure:20636: .../arm-linux-gcc -std=gnu99 -o conftest ... conftest.c
-lmagic -lpthread >&5
conftest.c:42:1: warning: function declaration isn't a
