Re: errors while building attk



I want to echo Malcolm's statements about LD_LIBRARY_PATH and
PKG_CONFIG_PATH, and to add that in my experience, you also need to set the
system path to point to the bin directory under the root folder where you
installing. In my system, I've got gnome-2.4 installed under
/opt/gnome-2.4/, so that tree has a bin, a lib, and other things which you
might expect to ... So, once I figured out that I needed to set my system
PATH variable to /opt.gnome-2.4/bin/, most of my errors went away and
everything built fine.

Hope this helps...

----- Original Message ----- 
From: "Malcolm Tredinnick" <malcolm commsecure com au>
To: <gnome-accessibility-list gnome org>
Sent: Wednesday, October 01, 2003 10:06 PM
Subject: Re: errors while building attk


On Thu, 2003-10-02 at 09:07, Alex Snow wrote:
> Hi all. I'm trying to build atk from source but havent gotten very
> far. I have glib-2.2.3 built and installed but the atk makefile
> doesn't seem to find the path correctly. when I run configure I don't
> get any errors but the make process fails.
> below is a script of the build process:
> Script started on Wed Oct  1 17:58:03 2003
> root skittles:~/build/atk-1.4.0# make
> make  all-recursive
> make[1]: Entering directory `/root/build/atk-1.4.0'
> Making all in atk
> make[2]: Entering directory `/root/build/atk-1.4.0/atk'
> ..//root/build/glib-2.2.3/gobject/glib-genmarshal --prefix=atk_marshal
> ./atkmarshal.list --header >> xgen-gmh \
> && (cmp -s xgen-gmh atkmarshal.h || cp xgen-gmh atkmarshal.h) \
> && rm -f xgen-gmh xgen-gmh~     \
> && echo timestamp > stamp-atkmarshal.h
> /bin/sh: line 1: ..//root/build/glib-2.2.3/gobject/glib-genmarshal: No
> such file or directory
> make[2]: *** [stamp-atkmarshal.h] Error 127
> make[2]: Leaving directory `/root/build/atk-1.4.0/atk'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/root/build/atk-1.4.0'
> make: *** [all] Error 2
> root skittles:~/build/atk-1.4.0# exit
> Script done on Wed Oct  1 17:58:13 2003
> I have all the sources in /root/build but it seems that the configure
> script didn't guess the path correctly...anyone have any ideas how to
> fix this?
> thanks!

Hmm, difficult to know how much to assume here. Apologies if I explain
some stuff you already know...

I assume you actually ran 'make install' for glib, not just 'make',
right? It is much practically impossible to build against uninstalled
stuff.

Assuming you have installed glib somewhere under /root/build/... you
will need to set the PKG_CONFIG_PATH environment variable to point to
/root/build/..../lib/pkgconfig, where "...." is to indicate that I don't
know the right prefix.

If you don't set this variable, then the configure script for atk will
try to use pkg-config to find the correct compile-time flags for
building against glib and will not pick up the new version you have
built.

Then you will need to set the LD_LIBRARY_PATH variable to the location
where the glib and atk libraries were installed before running anything,
otherwise applications which dynamically link against them will not find
the newly compiled version.

Cheers,
Malcolm
_______________________________________________
gnome-accessibility-list mailing list
gnome-accessibility-list gnome org
http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list




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