Make Check Failure Windows 10 install using Msys2

[mtvincen]

I am attempting to install on Windows 10 to use in emacs. I installed MSYS2 and updated pacman and installed the packages as described. I did not run ldconfig because I could not find a program that worked on windows. I ran the following commands

pacman -S base-devel mingw-w64-x86_64-toolchain mingw-w64-x86_64-libtool
autoreconf -vfi
./configure
make
make install
make check

This resulted in 14 failures: condition.dic, map.dic, rep.dic, ph2.dic, needaffix2.dic,compoundrules5.dic, checkcompoundrep.dic, checkcompoundcase2.dic, checkcompoundpattern.dic, checksharps.dic, i54633.dic, i54980.dic, 1463589.dic, encoding.dic

Below is the output of the make check

make[4]: *** [Makefile:1327: test-suite.log] Error 1
make[4]: Leaving directory '/c/users/matthew.vincent/.emacs.d/plugins/hunspell-master/tests'
make[3]: *** [Makefile:1435: check-TESTS] Error 2
make[3]: Leaving directory '/c/users/matthew.vincent/.emacs.d/plugins/hunspell-master/tests'
make[2]: *** [Makefile:1533: check-am] Error 2
make[2]: Leaving directory '/c/users/matthew.vincent/.emacs.d/plugins/hunspell-master/tests'
make[1]: *** [Makefile:1219: check-recursive] Error 1
make[1]: Leaving directory '/c/users/matthew.vincent/.emacs.d/plugins/hunspell-master/tests'
make: *** [Makefile:489: check-recursive] Error 1

when I run hunspell from the command prompt it returns:
Can't open affix or dictionary files for dictionary named "default".

Below is the file for the test-suit.log.

hunspell 1.7.0: tests/test-suite.log

TOTAL: 124

PASS: 110

SKIP: 0

XFAIL: 0

FAIL: 14

XPASS: 0

ERROR: 0

.. contents:: :depth: 2

FAIL: condition

=============================================
Fail in ./condition.good. Good words recognised as wrong:
r
ram
rach
FAIL condition.dic (exit status: 1)

FAIL: map

=============================================
Fail in ./map.sug. Bad suggestion?
1,3c1,3
< Fr hst ck
< t k rf r
< gro

Fr hst ck
t k rf r
gro
FAIL map.dic (exit status: 1)

FAIL: rep

=============================================
Fail in ./rep.sug. Bad suggestion?
7c7
< vinte e un

vinte
FAIL rep.dic (exit status: 1)

FAIL: ph2

=============================================
Fail in ./ph2.sug. Bad suggestion?
4,6d3
< wordstem
< stemword
< stemwordstem
FAIL ph2.dic (exit status: 1)

FAIL: needaffix2

=============================================
Fail in ./needaffix2.morph. Bad analysis?
analyze(foobar) = pa:foo st:foo id:3 pa:bar
stem(foobar) = foo
analyze(barfoo) = pa:bar st:bar pa:foo st:foo id:3
stem(barfoo) = barfoo
FAIL needaffix2.dic (exit status: 1)

FAIL: compoundrule5

=============================================
Fail in ./compoundrule5.morph. Bad analysis?
analyze(10%) = pa:1 st:1 po:num pa:0 st:0 po:num pa:% st:% po:sign_percent
stem(10%) = 10%
analyze(0.2%) = pa:0 st:0 po:num pa:. st:. po:sign_dot pa:2 st:2 po:num pa:% st:% po:sign_percent
stem(0.2%) = 0.2%
analyze(0.20%) = pa:0 st:0 po:num pa:. st:. po:sign_dot pa:2 st:2 po:num pa:0 st:0 po:num pa:% st:% po:sign_percent
stem(0.20%) = 0.20%
analyze(123.4561 ) = pa:1 st:1 po:num pa:2 st:2 po:num pa:3 st:3 po:num pa:. st:. po:sign_dot pa:4 st:4 po:num pa:5 st:5 po:num pa:6 st:6 po:num pa:1 st:1 po:num pa: st: po:sign_per_mille
stem(123.4561 ) = 123.4561
analyze(10) = pa:1 st:1 po:num pa:0 st:0 po:num
stem(10) = 10
analyze(0000) = pa:0 st:0 po:num pa:0 st:0 po:num pa:0 st:0 po:num pa:0 st:0 po:num
stem(0000) = 0000
analyze(10.25) = pa:1 st:1 po:num pa:0 st:0 po:num pa:. st:. po:sign_dot pa:2 st:2 po:num pa:5 st:5 po:num
stem(10.25) = 10.25
FAIL compoundrule5.dic (exit status: 1)

FAIL: checkcompoundrep

=============================================
Fail in ./checkcompoundrep.good. Good words recognised as wrong:
v
zszer
FAIL checkcompoundrep.dic (exit status: 1)

FAIL: checkcompoundcase2

=============================================
Fail in ./checkcompoundcase2.good. Good words recognised as wrong:

o

o

o

o
FAIL checkcompoundcase2.dic (exit status: 1)

FAIL: checkcompoundpattern

=============================================
Fail in ./checkcompoundpattern.good. Good words recognised as wrong:
k
nnysz
m
t
s
hossznyel
s
FAIL checkcompoundpattern.dic (exit status: 1)

FAIL: checksharps

=============================================
Fail in ./checksharps.good. Good words recognised as wrong:
m

ig
M

ig
M
SSIG
Aussto
Absto
Au
enabmessung
Prozessionsstra
e
Au
enma
e
FAIL checksharps.dic (exit status: 1)

FAIL: i54633

=============================================
Fail in ./i54633.good. Good words recognised as wrong:

diter

diter
FAIL i54633.dic (exit status: 1)

FAIL: i54980

=============================================
Fail in ./i54980.good. Good words recognised as wrong:
c
ur

uvre
C
UR

UVRE
FAIL i54980.dic (exit status: 1)

FAIL: 1463589

=============================================
Fail in ./1463589.sug. Bad suggestion?
1,5c1,5
< K hlschrank
< K hlschrank
< K hlschrank
< K hlschrank
< K hlschrank

K hlschrank
K hlschrank
K hlschrank
K hlschrank
K hlschrank
FAIL 1463589.dic (exit status: 1)

FAIL: encoding

=============================================
Fail in ./encoding.good. Good words recognised as wrong:
c
ur

uvre
C
UR

UVRE
FAIL encoding.dic (exit status: 1)

[mtvincen]

I was able to resolve the issue by searching and installing the hunspell diction
pacman -Ss hunspell

This showed that I had installed mingw but it did not find the dictionary that I was attempting to use.
mingw64/mingw-w64-x86_64-hunspell 1.7.0-5 [installed]
I was able to install the dictionary and it seems to be working in the command prompt
'pacman -S mingw64/mingw-w64-x86_64-hunspell-en'

However, I am still having issues connecting it with my emacs. I think it might be a result of the output when 'hunspell -D -a' is run. I think the first line of the output is messing up finding the correct paths. This is probably more of an ispell issue than it is a hunspell issue. I do like the idea that it shows that search path and the available dictionaries but it seems to mess with the I/O of the dictionaries. Maybe it would make sense to separate these output into different commands so that you can see the search path if you want but not require it in the directory output