su. den 17. 02. 2013 klokka 23.26 (+0100) skreiv Yamaban:
@Karl: To patch the Makefile to export the LANG=xx.UTF-8 you need, is a not nice way, but it may be helpful to start the fix.
Isolate what file comes out invalid, what is done to create this file, and maybe what singluar command causes the change from valid to invalid.
Then try to prefix just that command from <cmd> to LANG=xx.UTF-8 <cmd>.
Prefixing the ‘make’ command with ‘LC_ALL=en_US.UTF-8’ did the trick. Thanks everyone for the suggestion.
Try to contact upstream about the trouble, if upstream is NOT helful, make note about that in the changelog and the spec file.
Well, I’m actually both upstream and the packager in this case. And I don’t really see an easy way to fix this, except publishing the source code with the given file ‘pre-compiled’. The application (a command-line one) depends on being run in an UTF-8 environment, which is not really a problem, as ‘everyone’ uses UTF-8 today (people not doing this is not the target audience of this application, as it’s a dictionary application for words based on non-ASCII/Unicode characters). Basically, what the build step does is run awk, sort, grep and iconv on a UTF-8 text file to create a new text file. When run under the C locale, the first three commands don’t work properly (iconv complains about an ‘illegal input sequence’). But since ‘LC_ALL=en_US.UTF-8’ works, I’m basically happy. :) -- Karl Ove Hufthammer http://huftis.org/ Jabber: karl@huftis.org -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org