Complete.Org: Mailing Lists: Archives: freeciv-dev: May 2001:
[Freeciv-Dev] Re: gettext 0.10.37
Home

[Freeciv-Dev] Re: gettext 0.10.37

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Thue <thue@xxxxxxx>
Cc: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: gettext 0.10.37
From: Gaute B Strokkenes <gs234@xxxxxxxxx>
Date: 19 May 2001 23:39:50 +0100

On Sun, 20 May 2001, thue@xxxxxxx wrote:
> On Saturday 19 May 2001 23:42, Gaute B Strokkenes wrote:
>> On Sat, 19 May 2001, thue@xxxxxxx wrote:
> The context is this:
> 
>     AC_OUTPUT_COMMANDS(
>      [case " "$CONFIG_FILES" " in *" po/Makefile.in "* | *"
>         po/Makefile.in:"*) sed -e "/POTFILES =/r po/POTFILES"
>         po/Makefile.in > po/Makefile ;; esac])
> 
> So it seems to check if there is a po/Makefile.in in $CONFIG_FILES,
> and if there is it inserts the POTFILES which contains translateable
> strings into the right place.
> 
> A bit of history can be found at
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=94362

Thanks.  I think we can safely ignore this for the time being and let
upstream deal with it.

>> > Also, --with-included-gettext fails with this error:
>> > ---------------------
>> > make[2]: Entering directory `/mnt/data/freeciv-dev/gettext7/intl'
>> > gcc -c -DLOCALEDIR=\"/usr/local/share/locale\"
>> > -DLOCALE_ALIAS_PATH=\"/usr/local/share/locale\"
>> > -DLIBDIR=\"/usr/local/lib\" -DHAVE_CONFIG_H -I.. -I. -I../intl  -g -O2
>> > -Wall  dcigettext.c
>> > dcigettext.c:142: warning: static declaration for `mempcpy' follows
>> > non-static dcigettext.c:1199: parse error before `__extension__'
>> > dcigettext.c:1203: parse error before `{'
>> > dcigettext.c:142: warning: `mempcpy' declared `static' but never defined
>> > make[2]: *** [dcigettext.o] Error 1
>> > make[2]: Leaving directory `/mnt/data/freeciv-dev/gettext7/intl'
>> > make[1]: *** [all-recursive] Error 1
>> > make[1]: Leaving directory `/mnt/data/freeciv-dev/gettext7'
>> > make: *** [all-recursive-am] Error 2
>> > bash-2.05$
>> > ---------------------
>> > I looked a bit at it, and it occurs because HAVE_MEMPCPY is not defined,
>> > which it apperantly should be. If I kludge that away there seem to be
>> > more problems.
>>
>> Did you try removing config.cache and rerunning ./configure?  Does
>> the configure script mention 'checking for memcpy' or somesuch
>> anywhere in its output?
> 
> I did remove config.cache.  Actually the script does check for
> mempcpy inside a AC_CHECK_FUNCS, which should define HAVE_MEMPCPY
> correctly.

Yes, but what does it say when you run it?
  checking for memcpy... yes
or
  checking for memcpy... no
?

What does config.log say?

-- 
Big Gaute                               http://www.srcf.ucam.org/~gs234/
I HAVE to buy a new ``DODGE MISER'' and two dozen JORDACHE
 JEANS because my viewscreen is ``USER-FRIENDLY''!!


[Prev in Thread] Current Thread [Next in Thread]