Re: gnome-accessibility-list digest, Vol 1 #428 - 3 msgs

[Malcolm Tredinnick <malcolm commsecure com au>]

On Mon, May 05, 2003 at 10:01:02AM -0700, Don Raikes wrote:
> > I have justy built Garnome. It is in a separate user from anything else.
> > The user home directory contains .gconf, .gconfd, etc. Garnome itself is
> > in a directory called garnome. I then downloaded Gnoopernicus from Gnome
> > CVS andplaced it in the garnome directory. When I go to the gnopernicus
> > directory and type ./autogen.sh I get the following error messages:
> >
> > You need to install the gnome-common module and make
> > sure the gnome-autogen.sh script is in your $PATH.
> >
> I have just gone through this exercise.
> First of all, include the garnome/bin directory in your path.
> Second go to the garnome-0.23.1/gnome/gnome-common directory and type "make
> install".
> Garnome apparently sees no reason to build the common module. If there is no
> garnome-0.23.1/gnome/gnome-common directory, then you will need to download
> gnome-common from cvs and compile it.

The reason for this is that Garnome is designed to build from tarballs.
The gnome-common module is only relevant when building from CVS, so it
is never packaged up and distributed as a tarball.

The autogen.sh script that John's error message was referring to is a
common script from the gnome-common module. Once you install
gnome-common, you will get the required autogen.sh script "for free".

> As another hint, before trying to compile gnopernicus, gnome-mag, or
> gnome-speech, install libtool-1.4.1.  The libtool-1.4.3 has some issues
> compiling these modules.

Urgh, aargh! As somebody who gets to help debug these problems, can I just
say "please, don't". Libtool 1.4.1 is NOT supported for GNOME 2.0 and
beyond. There are some subtle bugs in it that makes life difficult. If
people are having problems with libtool 1.4.3, which is supported, we
should try to work out what is going wrong there. The libtool problems
you are seeing are not universal problems -- I have a fully built set of
accessibility applications using 1.4.3, for example.

I do not have a problem with people hacking about and changing things to
get something that works for them, but please do not recommend those
things to other people unless we know there is a real bug to work
around. I am not intending to flame anybody here (particularly Don, who
I realise has had some build problems and is persisting nonetheless),
but debugging these problems can be difficult and is made more so the
further you deviate from the standard setup.

Cheers,
Malcolm

-- 
Experience is something you don't get until just after you need it.