Re: Problems building CVS libbonobo with jhbuild

On Tue, 2004-07-27 at 15:47 +0100, Gustavo J. A. M. Carneiro wrote:
> A Ter, 2004-07-27 =C3=A0s 15:37, Keith Sharp escreveu:
> > Hello,
> >=20
> > I am trying to build libbonobo from CVS using jhbuild.  I am running
> > into the following error, which I have no idea how to fix:
> >=20
> > make[2]: Entering directory `/misc/gnome/build/libbonobo/activation-s=
erver'
> > bison -y -d -v ./activation-context-query-parser.y
> > rm -f y.output
> > touch stamp-parser
> > test -f y.tab.h && mv -f y.tab.h activation-context-query-parser.h ||=
 touch activation-context-query-parser.h
> > flex -t ./activation-context-query-lexer.l >activation-context-query-=
lexer.c
> > test -f y.tab.c && mv -f y.tab.c activation-context-query-parser.c ||=
 touch activation-context-query-parser.c
> > make[2]: *** No rule to make target `Bonobo_CosNaming_NamingContext.s=
erver', needed by `all'.  Stop.
> > make[2]: Leaving directory `/misc/gnome/build/libbonobo/activation-se=
rver'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/misc/gnome/build/libbonobo'
> > make: *** [all] Error 2
> > *** error during stage build of libbonobo: could not build module ***=
 [9/90]
>=20
>   It is intltool that takes care of generating
> Bonobo_CosNaming_NamingContext.server from
> Bonobo_CosNaming_NamingContext.server.in.  Do you have intltool properl=
y
> installed?  Also, Bonobo_CosNaming_NamingContext.server.in is generated
> from Bonobo_CosNaming_NamingContext.server.in.in by configure, so if yo=
u
> don't have that either you should try re-running configure.

I am not getting a Bonobo_CosNaming_NamingContext.server.in generated in
libbonobo/activation-server/.  I looked at configure.in and I had
expected to see this Bonobo_CosNaming_NamingContext.server.in listed in
the AC_OUTPUT section but I don't.

I am using jhbuild as follows:

jhbuild bootstrap
jhbuild update
jhbuild build --clean --no-network --autogen

The bootstrap has downloaded intltool, the NEWS file indicates version
0.31.  Is this sufficiently recent, or maybe even too recent?

Thanks for your help,

Keith.=20