Hi Matt,

  Here's your answer:  create a link in the folder /bin that will direct the 
AbiWord installation script to where your glib-config and gtk-config files 
are (in my case /opt/gnome/bin).
  In my situation, I just typed 'make' then 'make install'.  Voila.
  Cheers.
-- 
Matt Cahill
mailto:[EMAIL PROTECTED]


On October 27, 2001 09:07 pm, Matt C. wrote:
> Hello,
>
>   This is my first post to the list, and I'm very much looking forward to
> using AbiWord 9.4.1 (I currently use 0.7).
>   I'm running Slackware 8.0, and I've come across the following problem
> during the make/install process (using the UNIX source tarball, not the
> rpm):
>
> <snip from Konsole>
>
> make[5]: Leaving directory `/home/matt/temp/abiword-0.9.4.1/psiconv'
> Build requirements satisfied.
> make[4]: Leaving directory
> `/home/matt/temp/abiword-0.9.4.1/abi/src/config/require/xp'
> make  ABI_ROOT=/home/matt/temp/abiword-0.9.4.1/abi/src/.. -C unix build
> make[4]: gnome-config: Command not found
> make[4]: Entering directory
> `/home/matt/temp/abiword-0.9.4.1/abi/src/config/require/unix'
> make[4]: gtk-config: Command not found
> `@`@make[4]: gtk-config: Command not found
> `@`@make[4]: gnome-config: Command not found
> `@`@make[4]: glib-config: Command not found
> `@`@Building with [LicensedTrademarks:Off Debug:Off BiDi:Off Bonobo:Off
> Gnome:On LibXML:Off Pspell:Off Scripting:Off].
> TODO do we need to test for GCC or EGCS and a version number?
> /bin/sh: glib-config: command not found
> glib not found
> make[4]: *** [_GLIB_] Error 1
> make[4]: Leaving directory
> `/home/matt/temp/abiword-0.9.4.1/abi/src/config/require/unix'
> make[3]: *** [build] Error 2
> make[3]: Leaving directory
> `/home/matt/temp/abiword-0.9.4.1/abi/src/config/require'
> make[2]: *** [build] Error 2
> make[2]: Leaving directory `/home/matt/temp/abiword-0.9.4.1/abi/src/config'
> make[1]: *** [build] Error 2
> make[1]: Leaving directory `/home/matt/temp/abiword-0.9.4.1/abi/src'
> make: *** [install] Error 2
> bash-2.05#
>
> </snip from Konsole>
>
>   I compiled this in KDE (with and without the GNOME option).  I use KDE
> most often, but I do have GNOME and it works when I need to get into it
> (which isn't often).  Can I assume from the print-out that the problem lies
> in my version of glib?
>
>   Any help appreciated  :)

-- 
My Very Best to You,

Matt Cahill
mailto:[EMAIL PROTECTED]


-----------------------------------------------
To unsubscribe from this list, send a message to
[EMAIL PROTECTED] with the word
unsubscribe in the message body.

Reply via email to