1 |
I have trouble building minicom-1.83.1, I get the following two suspect |
2 |
passages in the build: |
3 |
|
4 |
--- snip |
5 |
|
6 |
msgfmt -o ja.mo ja.po |
7 |
ja.po: warning: Charset "euc-japanese" is not a portable encoding name. |
8 |
Message conversion to user's charset might not work. |
9 |
cc ujis2sjis.c -o ujis2sjis |
10 |
./ujis2sjis <ja.po >ja_JP.SJIS.po |
11 |
msgfmt -o ja_JP.SJIS.mo ja_JP.SJIS.po |
12 |
ja_JP.SJIS.po: warning: Charset "euc-japanese" is not a portable encoding name. |
13 |
Message conversion to user's charset might not work. |
14 |
|
15 |
--- snip |
16 |
|
17 |
and |
18 |
|
19 |
--- snip |
20 |
|
21 |
msgfmt -o ko.mo ko.po |
22 |
ko.po:131: invalid multibyte sequence |
23 |
ko.po:917: invalid multibyte sequence |
24 |
ko.po:1095: invalid multibyte sequence |
25 |
ko.po:1992: invalid multibyte sequence |
26 |
ko.po:2039: invalid multibyte sequence |
27 |
found 5 fatal errors |
28 |
make[1]: *** [ko.mo] Error 1 |
29 |
make[1]: Leaving directory `/tmp/portage/minicom-1.83.1/work/minicom-1.83.1/src/po' |
30 |
|
31 |
--- snip |
32 |
|
33 |
If I didn't know better, I'd say there's some kind of version mismatch |
34 |
with gettext. Even when I rsynced < 10 mins ago, there is only one gettext |
35 |
ebuild. |
36 |
|
37 |
Has anybody else gotten minicom to compile lately ? |
38 |
|
39 |
Regards, |
40 |
|
41 |
Karl T |