Re: Pango / Xrender / Red Hat 8.0

[Carson Gaspar <carson+garnome taltos org>]

--On Tuesday, July 12, 2005 7:40 PM +1000 Paul Drain <pd cipherfunk org> 
wrote:

> Actually, it does :)
>
> The problem exists when there are some GARNOME and non-GARNOME (system)
> libraries detected by the same application. If you choose to modify your
> own export variables when building GARNOME:
>
> * PATH ($GARNOME/bin|sbin)
> * LD_LIBRARY_PATH ($GARNOME/lib)
> * PKG_CONFIG_PATH ($GARNOME/lib/pkgconfig)
>
> and:
>
> * GNOME2_PATH ($GARNOME/)
>
> Should all be correctly set before you start, then GARNOME will
> hopefully find everything in the right order ...
>
> ... maybe :)

Sadly, no. The problem is the configure scripts - they're just broken for 
anyone who wants to override system some libs and use others. Of course 
this is not a configuration they're designed for... The general problem is 
that they prepend lib/include dirs instead of appending them. So no matter 
how many ways you stuff $GARNOME in, it won't be searched first.

You have a few choices:

- build _everything_ in $GARNOME, including your X libs, so the configure 
scripts won't find the system lib dirs
- link/copy the system bits into $GARNOME, and edit the .pc files in 
$GARNOME to point to the $GARNOME paths
- every time the link breaks fix the configure scripts and submit patches

The good news is that, as of the last time I built garnome on Solaris, you 
only have to hack 2 or 3 configure files to fix the include/link order.

--
Carson