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: Gaute B Strokkenes <gs234@xxxxxxxxx>
Cc: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: gettext 0.10.37
From: Thue <thue@xxxxxxx>
Date: Sun, 20 May 2001 00:45:20 +0200

On Sunday 20 May 2001 00:39, Gaute B Strokkenes wrote:
> >> > 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?

Umm, sorry.
it said "yes".

-Thue


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