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?
Regards,
Jeremy Henty
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
