cups-filters-1.0.19 uses PKG_CHECK_MODULES([IJS], [ijs]) macro to find module providing libijs. We ship libijs in ghostscript, but don't ship %{_libdir}/pkgconfig/ijs.pc so running configure in cups-filters ends up with: checking for IJS... no configure: error: Package requirements (ijs) were not met: No package 'ijs' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables IJS_CFLAGS and IJS_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. Shipping that pkgconfig file fixes the problem. Is there any reason we haven't done so ? === Suggested fix === diff --git a/ghostscript.spec b/ghostscript.spec @@ -241,9 +241,8 @@ # Documentation install -m0644 doc/COPYING $RPM_BUILD_ROOT%{_docdir}/%{name}-%{gs_dot_ver} -# Don't ship pkgconfig or libtool la files. -rm -f $RPM_BUILD_ROOT%{_libdir}/pkgconfig/ijs.pc \ - $RPM_BUILD_ROOT%{_libdir}/libijs.la +# Don't ship libtool la files. +rm -f $RPM_BUILD_ROOT%{_libdir}/libijs.la # Don't ship ijs example client or server rm -f $RPM_BUILD_ROOT%{_bindir}/ijs_{client,server}_example @@ -325,6 +324,7 @@ %dir %{_includedir}/ijs %{_includedir}/ijs/* %{_bindir}/ijs-config +%{_libdir}/pkgconfig/ijs.pc %{_libdir}/libijs.so %{_libdir}/libgs.so
Note: cups-filters < 1.0.19 used to use the following code (configure.ac) to find libijs AC_CHECK_LIB(ijs,main, [ IJS_LIBS=-lijs], [ echo "*** ijs library not found. ***";exit ] ) AC_SUBST(IJS_LIBS) which was OK with ghostscript.
I think the only reason we didn't do it was because nothing needed it.