From: Chris Vine (chris_at_cvine.freeserve.co.uk)
Date: Mon Nov 17 2003 - 16:37:13 EST
On Monday 17 November 2003 1:45 am, Ted Parks wrote:
> Chris,
> I am trying to build Abiword from source because no rpm package of the
> 2.0 release exists for RedHat 8.0. As I recall from what has proven a
> lengthy process, I was trying to build pango in order to upgrade gtk.
> When I try to configure Abiword, I get the following error:
>
> checking GTHREAD_LIBS... -pthread -L/usr/local/lib -lgthread-2.0 -lglib-2.0
> checking for
> gtk+-2.0 >= 2.0
> libglade-2.0 >= 2.0.0
> ... Package gtk+-2.0 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `gtk+-2.0.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'gtk+-2.0' found
> configure: error
>
> I believe gtk+-1.2.10-22 is the version currently installed on my
> system. The "build" document from Abiword says that the application
> requires gtk+-2.0. From your last posting, I sense that I need to
> install glib 2.0, not 2.2, for gtk+-2.0. The expression "environmental
> variable LD_LIBRARY_PATH," however, is unclear to me. How do I change
> this "variable"? Where is it?
gtk+-1.2 is too old, but IS parallel installable with gtk+-2, so you don't
need to uninstall the old version.
You seem to have got binary RPMs now, which is the best way of doing it. But
if you want to compile the necessary bits of GNOME-2 for abiword from
sources, go to the gnome download site and download the glib, pango, gtk+ and
libglade sources for the latest version (GNOME-2.4.0), uninstall the binary
RPMs of these and compile the source packages. However as you now have a
working Gtk+-2 installation from RPMs my strong recommendation is to leave
these as they are.
Note that if you install these in /usr/local, which is the default, then
/usr/local/lib/pkgconfig must be in your PKG_CONFIG_PATH.
If you want to compile abiword from source and you stick with the glib, pango,
gtk+ and libglade RPMs as I suggest, you will need the *-devel packages for
these also and any other relevant libraries (such as fribidi, zlib, libpng
and libxml2 - see abiword-{version}/abi/docs/build/BUILD.TXT for a list).
You can then build abiword in the usual way, but you might want to note a few
points I found when compiling it:
Before configuring abiword with ./configure:
(i) place the gzipped abiword-plugins source package in the abiword directory,
and gunzip it.
(ii) the build system for *nix seems to assume that you have a precompiled
version of libwv installed in your system, and I do not. As libwv is
pre-prepared in the abiword source package for windows and not for *nix, I
had to run autogen.sh in abiword-{version}/wv to provide the correct build
system, configure it with --enable-static flag, and then make libwv. In
addition, in order for abiword to find the compiled libwv in the abiword
build tree without actually installing it in my system I had to make a
symbolic link from abiword-{version}/wv/.libs/libwv.a to
abiword-{version}/wv/lilwv.a.
After that you can ./configure and build abiword followed by abiword-plugins,
and install them.
Chris.
-----------------------------------------------
To unsubscribe from this list, send a message to
abiword-user-request_at_abisource.com with the word
unsubscribe in the message body.
This archive was generated by hypermail 2.1.4 : Mon Nov 17 2003 - 16:36:40 EST