Jeremy Henty wrote:
Wayne Blaszczyk wrote:
Today I had a closer look at the enchant-2.1.3 build and noticed
that it installs /usr/bin/enchant-2 .
It also installs enchant-2.pc instead of enchant.pc . On my system,
after installing 2.1.3 but not having cleaned up 2.1.2 :
$ pkg-config --list-all | grep enchant
enchant-2 libenchant - A spell checking library
enchant libenchant - A spell checking library
$ pkg-config --modversion -- enchant enchant-2
2.1.2
2.1.3
$
So if the configure script is still looking for a package called
enchant instead of enchant-2, that might explain why upgrading to
enchant-2.1.3 could break things so badly.
It is hard to believe that someone would upgrade the major version of
a package in a release that presents itself as a point version update.
Yet how else can we understand this?
Indeed. I have both installed:
$ diff -u enchant*.pc
--- enchant-2.pc 2017-11-30 14:16:41.147202157 -0600
+++ enchant.pc 2017-11-29 20:03:14.376527275 -0600
@@ -5,7 +5,7 @@
Name: libenchant
Description: A spell checking library
-Version: 2.1.3
+Version: 2.1.2
Requires.private: glib-2.0 gmodule-no-export-2.0
-Libs: -L${libdir} -lenchant-2
-Cflags: -I${includedir}/enchant-2
+Libs: -L${libdir} -lenchant
+Cflags: -I${includedir}/enchant
Sot we may just need to do (as root):
ln -svf enchant-2.pc /usr/lib/pkgconfig/enchant.pc
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
