Hi,
On Fri, 16 May 2025, Vincent Belaïche wrote:
Hello,
My answer inserted below,
De : Kevin Atkinson <kev...@gnu.org>
Envoyé : jeudi 15 mai 2025 18:35
À : Vincent Belaïche <vincent....@hotmail.fr>
Cc : aspell-devel@gnu.org <aspell-devel@gnu.org>
Objet : Re: ASPELL aspell-0.60.8.1 compilation failure on MSYS2 + MINGW64
However, this could be automated by having somewhere in the
m4/lib-link.m4 or m4/lib-prefix.m4 the appropriate autotools M4 macro
for calling (cygpath -m PREFIX) under the hood when the target is
MINGW. This would certainly greatly help MSYS2/pacman repo
maintainers to compile aspell properly.
There is a chance this might already be fixed with newer versions of
autotools. If possible try updating the versions of autotools to the
latest and see if that helps (the script ./maintainer/autogen might
help if you are using the release tarball, although you might have
better luck if you checkout the version from git).
Actually I had tried this, I have this error when lauching ./autogen.sh:
/THE/BUILD/DIRECTORY/aspell/gnulib/gnulib-tool.py: *** minimum supported
autoconf version is 2.64. Try adding AC_PREREQ([2.64]) to your configure.ac.
/THE/BUILD/DIRECTORY/aspell/gnulib/gnulib-tool.py: *** Stop.
Offhand I have no idea. My only suggestion is to try using a clean
checkout from git and if that doesn't work try what it suggests.
I will look into upgrading to the newest versions of autotools for the next
release.
The other issue that I had is that Emacs ispell.el needs also to know
where the dictionaries are located because it builds some
auto-completion list to help the user select a dictionary amongst
those available. To get this, Emacs ispell calls « aspell -vv » and
expects to find something like
LIBDIR = "c:/msys64/mingw64/lib/aspell-0.60"
in the output, where "c:/msys64/mingw64" is whatever prefix the user
configured at install. This also does not work, so I did some hack
which I attached.
This is not a windows specific issue. The correct way to get this
information from aspell is:
aspell config dict-dir
Kevin
Great, when time allows I will submit a patch to Emacs ispell.el in
order to fix this and use the correct way.
Thanks.
Kevin
