[Q] Where and what is t-cs.gmo?

[Maurice Volaski]

>On Fri, Apr 09, 2004 at 03:58:03AM -0400, Maurice Volaski wrote:
>>  Compiling e2fsprogs-1.35 under Linux complains....
>>
>>  make[2]: Entering directory `/src/kernel/e2fsprogs-1.35/po'
>>  : --update cs.po e2fsprogs.pot
>>  rm -f cs.gmo && : -c --statistics -o cs.gmo cs.po
>>  mv: cannot stat `t-cs.gmo': No such file or directory
>>  make[2]: *** [cs.gmo] Error 1
>>  make[2]: Leaving directory `/src/kernel/e2fsprogs-1.35/po'
>>  make[1]: *** [all-progs-recursive] Error 1
>>  make[1]: Leaving directory `/src/kernel/e2fsprogs-1.35'
>>  make: *** [all] Error 2
>
>Try using "configure --with-include-gettext".  That should solve the
>problem; it's caused by your system having too old a copy of the
>gettext library, and automatic autoconf macros supplied by gettext
>aren't particularly good at handling backwards compatibility with
>older gettext implementations.

I didn't seem to have gettext at all, so I installed version 0.14.1. 
And ./configure said:

checking for xgettext... (cached) no

despite
whereis xgettext
xgettext: /usr/local/bin/xgettext

Then I found an option to configure using the included gettext as you 
mention above. That initially gave

/bin/chmod +x mk_cmds
../et/compile_et --build-tree ./ss_err.et
../et/compile_et: /usr/bin/awk: No such file or directory
../et/compile_et: /usr/bin/awk: No such file or directory
make[2]: *** [ss_err.c] Error 127

which I now realize occurs because it is hard-coded to look for awk 
in /usr/bin.

I just tried again after symlinking awk in /usr/bin and got:

: multiple definition of `_nl_find_msg'
../intl/libintl.a(dcigettext.o)(.text+0x6d8):/src/kernel/e2fsprogs-1.35/intl/dcigettext.c:698: 
first defined here
/usr/bin/ld: Warning: size of symbol `_nl_find_msg' changed from 1325 
in ../intl/libintl.a(dcigettext.o) to 1309 in 
../intl/libintl.a(dcigettext.o)


>build process, and everything else important has been built.  So if
>you don't care about seeing e2fsck messages being output in Polish or
>Turkish, you can just ignore the errors.  :-)

I just ended up compiling with  ./configure --disable-nls
-- 

Maurice Volaski, mvolaski at aecom.yu.edu
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University