Re: postgresql-7.3.4 - undefined reference to `libintl_gettext' - Mailing list pgsql-ports

From Tom Lane
Subject Re: postgresql-7.3.4 - undefined reference to `libintl_gettext'
Date
Msg-id 1036.1065215494@sss.pgh.pa.us
Whole thread Raw
In response to postgresql-7.3.4 - undefined reference to `libintl_gettext'  (blue <blue@DELETETHISwave460.net>)
Responses Re: postgresql-7.3.4 - undefined reference to `libintl_gettext'
List pgsql-ports
blue <blue@DELETETHISwave460.net> writes:
> main/SUBSYS.o(.text+0xcc): undefined reference to `libintl_bindtextdomain'
> main/SUBSYS.o(.text+0xd9): undefined reference to `libintl_textdomain'
> main/SUBSYS.o(.text+0x16f): undefined reference to `libintl_gettext'
> main/SUBSYS.o(.text+0x1b1): undefined reference to `libintl_gettext'
> main/SUBSYS.o(.text+0x26d): undefined reference to `libintl_gettext'
> [etc]

Hm, that's interesting, because in the sources those calls are just
'bindtextdomain' etc.  It looks like you are including files that define
bindtextdomain et al as macros for libintl_bindtextdomain et al.  The
copy of <libintl.h> I have here doesn't do that, but there may be other
versions that do.  I'd say that you have header files that don't match
up with your library that defines gettext --- or at least, configure
managed to find an implementation of gettext that didn't match the
headers.  Check your inclusion and search paths.

Peter: is our configure stuff actually able to cope with this?  It looks
to me like configure will look for a library providing "gettext", when
it would need to look for "libintl_gettext".  Or should we just state
that such-and-such an implementation is too broken to use?

            regards, tom lane

pgsql-ports by date:

Previous
From: blue
Date:
Subject: postgresql-7.3.4 - undefined reference to `libintl_gettext'
Next
From: Peter Eisentraut
Date:
Subject: Re: postgresql-7.3.4 - undefined reference to `libintl_gettext'