Description Rainer Hurling 2016-01-13 10:56:40 UTC

Created attachment 165492 [details]
patch to make the build of german/hunspell independend from locale settings

I am not able to build german/hunspell for some time now:


[..snip..]
cat hunspell-capmain-plus_de_CH.tmp.unfiltered-list.tmp | ( sed -f ./bin/dic2iso | aspell --encoding=iso8859-1 --lang=de_CH --local-data-dir=./aspell expand ) > hunspell-capmain-plus_de_CH.tmp.unfiltered-list-expanded.tmp
sed -f ./bin/dic2iso < hunspell-capmain-plus_de_CH.tmp.unfiltered-list-expanded.tmp |sed "s/qq//g" | nl | hunspell `hunspell -h 2>&1 | grep -q "hunspell \\-i" && echo "-i latin1"` -d hunspell/de_CH_small -L > hunspell-capmain-plus_de_CH.tmp.unknown.tmp
error: line 1: missing or bad word count in the dic file
Hash Manager Error : 4
sed "s/^ *\([0-9]*\)\t.*$/\1/" hunspell-capmain-plus_de_CH.tmp.unknown.tmp > hunspell-capmain-plus_de_CH.tmp.list-unknown-lines.tmp
./bin/extractlines.pl hunspell-capmain-plus_de_CH.tmp.list-unknown-lines.tmp hunspell-capmain-plus_de_CH.tmp.unfiltered-list.tmp > hunspell-capmain-plus_de_CH.tmp.tmp
./bin/hunspell-capmain hunspell-capmain-plus_de_CH.tmp.tmp | sed -f ./bin/iso2dic > hunspell-capmain-plus_de_CH.tmp
sed: 3: ./bin/iso2dic: RE error: illegal byte sequence
+ INFILE=hunspell-capmain-plus_de_CH.tmp.tmp
+ test -z hunspell-capmain-plus_de_CH.tmp.tmp
+ grep $'^[A-Z\304\326\334\311]' hunspell-capmain-plus_de_CH.tmp.tmp
+ grep -v -- --x
+ ./bin/myspellfixprefix.pl
+ ./bin/lcfirst.pl
+ sed 's:$:/ozm: ; s:/\(.*\)/:/\1: ; s:--x::'
+ echo
Makefile:341: die Regel für Ziel „hunspell-capmain-plus_de_CH.tmp“ scheiterte
gmake[2]: *** [hunspell-capmain-plus_de_CH.tmp] Fehler 1
gmake[2]: Verzeichnis „/usr/ports/german/hunspell/work/igerman98-20151222“ wird verlassen
===> Compilation failed unexpectedly.


This error was reported some years ago in a mail[1] and as bug #175423, but seems not definitely solved?

As far as I can see, it is a problem with the locale environment, especially with some LANG= settings, for example with LANG=de_DE.UTF-8. Probably, it occurs on from the latest UTF changes in base?

If I unset LANG= or set it to LANG=C, all builts fine. The appended patch solved the problem for at least my german locale settings.

My boxes run a very recent FreeBSD 11.0-CURRENT amd64.


[1] http://lists.freebsd.org/pipermail/freebsd-office/2011-August/000084.html