[wplug] SuSE 9.1 glib2 errors.

[Robert E. Coutch]

glib files are at:
 /opt/gnome/glib

glib2 files are in:
 /opt/gnome/lib

Not sure where the glib-devel would be since I don't have it installed (yet).

On Thursday 26 August 2004 10:02 pm, Christopher DeMarco wrote:
> On Thu, Aug 26, 2004 at 05:32:27PM -0400, Karlos Abel wrote:
> > Sorry for  the timidity, but I've been  on other mailing lists where
> > newbies weren't exactly welcomed.
>
> Mmm.  Fresh meat.
>
> > 1.  Where did YAST2 stash my glib and glib-devel?
>
> SuSE is RPM-based.  Search all your RPMs for the glib packages:
>
>   rpm -qa | grep glib
>
> Now list the files in the package:
>
>   rpm -ql glib-whatever-the-name-is
>
> > 2.  How do I tell a configure script to find it?
>
> Wow - can't get the package to work so you compile  it yourself.  Good
> man.
>
> Get a list of options that configure can take:
>
>   ./configure --help
>
> You're looking for the override for the library location.  Something
> *similar to*
>
>   ./configure --with-glib=/usr/lib/suse/puts/it/here/glib
>
> > 3.  How do I avoid this in the future?
>
> Stop using SuSE ;)
>
> Seriously, the reason  that RPMs and DEBs  and ebuilds and ports exist
> is  because building source isn't for  Aunt  Tillie; it can be tricky.
> Learn how  and  why (and whether!)  the process  I've  shown works and
> you'll be free from reliance on YAST2.
>
> N.b. that compiling   a package from source  is  outside the  scope of
> YAST2, and you won't be able to remove/upgrade GAIM from YAST2.
>
> > I can provide detailed, reproducable error messages if needed.
>
> You should always assume  that we want  this.  Post as much detail  as
> you have,  don't waste your time  asking because 90%  of  the time for
> non-trivial problems we want the diagnostics.
>
> Here is the canonical  guide to making sure you  don't get scolded for
> being "that annoying newbie".  It  will co-incidentally also guide you
> to more careful, methodical problem solving:
>
> http://www.catb.org/~esr/faqs/smart-questions.html