Description of problem: I am trying to build libvmi on Fedora 35, but the build fails due to a bad compiler flag. Fedora 34 works. Version-Release number of selected component (if applicable): cmake-3.22.0-4.fc35.x86_64 How reproducible: Every time Steps to Reproduce: Building libvmi-0.14.0 on Fedora 35 with the following commands results in the indicated error: $ mkdir build $ cd build $ cmake .. $ make VERBOSE=1 [...] /usr/bin/cc -Wall -Wextra -g -g3 -O0 -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now -rdynamic CMakeFiles/map-addr.dir/map-addr.c.o -o map-addr -Wl,-rpath,/home/mike/Download/libvmi-0.14.0/build/libvmi ../libvmi/libvmi.so.0.0.14 -L/usr/lib64glib-2.0 /usr/bin/ld: ../libvmi/libvmi.so.0.0.14: undefined reference to `g_direct_hash' /usr/bin/ld: ../libvmi/libvmi.so.0.0.14: undefined reference to `g_tree_new_full' /usr/bin/ld: ../libvmi/libvmi.so.0.0.14: undefined reference to `g_slist_free_full' [...] collect2: error: ld returned 1 exit status Notice the use of "-L/usr/lib64glib-2.0". A '/' is missing from the path, and the directory contains headers, not libraries. Additional info: See also https://github.com/libvmi/libvmi/issues/1002.
This is actually a bug in libvmi itself, as it doesn't use the output of pkgconfig properly. Fixed by https://src.fedoraproject.org/rpms/libvmi/c/3d132c9990c0377fcf1b7c7faea159d4d5e9722a
Successful builds: F35: https://koji.fedoraproject.org/koji/buildinfo?buildID=1867135 Rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=1867134
Thank you, Björn!
(In reply to W. Michael Petullo from comment #3) > Thank you, Björn! You're welcome!