Re: Problems Compiling GConf2



On Thu, 2003-07-17 at 06:58, Rich Caloggero wrote:
> I've tried the version in the 2.3.4 sources and the 2.2.2 sources (
> tarballs ). Here's what make says. Note: there were about 30 more lines
> which looked, to the untrained ear, like the ones included here.
> 
> 
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I.. -I../gconf -DORBIT2=1 -pthread -I
> /us
> r/local/include/orbit-2.0 -I/usr/local/include/linc-1.0 -I/usr/local/include
> /lib
> xml2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DGCONF_ENABLE_INTE
> RNAL
> S=1 -DG_LOG_DOMAIN=\"GConf-Backends\" -g -O2 -Wall -c
> markup-tree.c  -fPIC -DPIC
>  -o .libs/markup-tree.o
> markup-tree.c:2919: parse error before "FILE"
> markup-tree.c:2922: parse error before "FILE"
> markup-tree.c:2926: parse error before "FILE"
> markup-tree.c:2932: parse error before "FILE"
> markup-tree.c: In function `write_value_element':
> markup-tree.c:2939: warning: implicit declaration of function `fprintf'
> markup-tree.c:2939: `f' undeclared (first use in this function)
> ... etc ...

This looks for all the world like a "#include <stdio.h>" did not work
somewhere. A bit confusing; I am not really sure what is going wrong
here, but it is something peculiar to your system, I suspect.

Another thing I notice from the build line is that some files are being
included from /usr/local/include/ (ORBit-2.0, Linc, libxml2, etc) and
others from /usr/include (glib-2.0). Is this what you are expecting to
happen, or are you trying to build all of GNOME under /usr/local? Note
that what I have mentioned is not necessarily a problem, but it may be
symptomatic of pkg-config confusions or mismatched packages or
something.

I was able to build gconf (admittedly from CVS rather than tarballs)
without problems a day ago.

Malcolm




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