pan-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Pan-users] Gettext errors when compiling 0.131


From: David Shochat
Subject: Re: [Pan-users] Gettext errors when compiling 0.131
Date: Thu, 19 Jul 2007 20:14:43 -0400
User-agent: Thunderbird 2.0.0.4 (X11/20070604)

Benjamin Esham wrote:
Hello all,

I'm running Mac OS X with Fink, and building Pan 0.131 from source myself.
I recently ran debfoster in an attempt to weed out packages I no longer
need, and of course Pan will no longer compile.  I rebuilt fresh copies of
libpcre, gtk+2, and gmime, but when compiling I get this:

if g++ -DHAVE_CONFIG_H -I. -I. -I../..  -I../.. -I/sw/include/glib-2.0 
-I/sw/lib/glib-2.0/include -I/sw/include/gmime-2.0   -I/sw/include/glib-2.0 
-I/sw/lib/glib-2.0/include     -g -O2 -MT filter-info.o -MD -MP -MF 
".deps/filter-info.Tpo" -c -o filter-info.o filter-info.cc; \
then mv -f ".deps/filter-info.Tpo" ".deps/filter-info.Po"; else rm -f 
".deps/filter-info.Tpo"; exit 1; fi
In file included from filter-info.cc:23:
/sw/include/glib-2.0/glib/gi18n.h:23:21: error: libintl.h: No such file or 
directory
...
This sounds very familiar. I ran into the same problem under DarwinPorts (now called MacPorts). I came up with a workaround and then Charles identified the real problem as being the pkg-config file for glib-2.0. I think the key post in the thread is this:

http://lists.gnu.org/archive/html/pan-users/2006-07/msg00133.html

I wrote a bug report against DarwinPorts to fix this and I believe that is why this particular problem no longer occurs in MacPorts. But you can just modify your glib-2.0.pc by adding -I${includedir} to the Cflags: line. I see that on my Mac version (the Ubuntu version doesn't need it since in that case ${includedir} is just /usr/include which contains libintl.h). On the Mac, libintl.h is not in /usr/include. It is in the special include directory that belongs to MacPorts (I assume it's the same situation with fink) and that's why that directory has to be explicitly included.
-- David






reply via email to

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