Description of problem: libXmu-devel should depend on pkgconfig. And also configure generated by PKG_CHECK_MODULES(BMTOA, x11 xmu) in a configure.ac fails if libXext-devel isn't installed explicitely (but libXmu-devel is). So I think libXmu-devel should depend on libXext-devel, or the .pc file should be changed, since I guess this dependency comes from: Requires.private: x11 xt xext Version-Release number of selected component (if applicable): libXmu-devel-1.0.2-5 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Dependency on pkg-config added in rawhide. However, libXmu-devel shouldn't doesn't depend on libXext-devel as far as I can see. ldd /usr/lib/libXmu gives [krh@dinky devel]$ ldd /usr/lib/libXmu.so.6.2.0 ... libXext.so.6 => /usr/lib/libXext.so.6 (0x00dcf000) ... which means that rpm automatically pulls in libXext as a dependency of libXmu. However pkg-config --libs xmu gives: [krh@dinky devel]$ pkg-config --libs xmu -lXmu -lXt -lX11 which means that libXext-devel is not a build time dependency for applications using libXmu-devel. Furthermore, libXext-devel doesn't install any header files.
Here is the pkg-config invocation that fails: [dumas@localhost ~]$ pkg-config --exists --print-errors "x11 xmu" Package xext was not found in the pkg-config search path. Perhaps you should add the directory containing `xext.pc' to the PKG_CONFIG_PATH environment variable Package 'xext', required by 'Xmu', not found [dumas@localhost ~]$ echo $? 1 So even though it doesn't show it, it needs it.
Ah, yes. OK, 'Requires: libXext-devel' added to libXmu-devel. It's a low-impact fix though (if you're doing X development, you probably have libXext installed), so I'm just going to build it for rawhide (i.e. to be fc7).
Not that low-impact, since this issue shows up in mock. It forces all the packages which depends on Xaw to add a dependency although they don't depend directly on Xext.