Re: more broken installers

[Don Dudley <donedudley yahoo com>]

You might try checking the version of Gnome you're
running.  I know that if it isn't the latest, and
you're trying to install the latest version of some
gnome tool, you'll bang into every dependency and
sub-dependency of every library and package that the
tool requires.  Depending on what and how many tools
you install, you may be practically installing the
whole gnome desktop a piece at a time!

The simplest solution may be to start by installing
the latest version (2.4.4) of the desktop, which will
have latest of all the packages and libraries the
tools depend on.  I think you'll find you'll have a
much better time of it.

--- Anthony <orders nodivisions com> wrote:
>  > PKG_CONFIG_PATH
> 
> Chee Bin HOH has been emailing me directly, and that
> was one of the 
> things he mentioned.  It worked for ggv.  But then I
> got to gnome-media, 
> and it completely ignored PKG_CONFIG_PATH as well as
> the other vars and 
> command-line args that I specified, and STILL
> insisted on looking in 
> /usr/bin.
> 
>  > There are (at least) two conventions for where to
> install things in a
>  > linux system. When using any given convention,
> you have to take
>  > specific, explicit steps to tell the
> compile/install process to also
>  > use the other convention when resolving
> dependencies etc.
> 
> Yes.  Like:
> 
> 	LDFLAGS
> 	LD_LIBRARY_PATH
> 	PKG_CONFIG_PATH
> 	--prefix
> 	--libdir
> 
> But it doesn't matter if you set them, when the
> installer completely 
> ignores them.  The problem here isn't my setting
> these things; the 
> problem is that the installers keep finding ways
> around those settings, 
> and looking where they want to instead.
> 
>  > Its basically a total nightmare.
> 
> Aha!  That is the magic phrase that I was waiting
> for someone else to 
> say.  Thank you.  I have spent over a week on this
> nonsense, hitting the 
> exact same problem over and over, but having the
> previous solution fail 
> for the next package.  Completely ridiculous.
> 
> I'm trying dropline Gnome now and, failing that, I'm
> doing an "upgrade" 
> install from the lastest slackware-current CD.  Even
> if I have to 
> re-install my applications, that would be a treat
> compared to wrestling 
> with this crap for weeks.
> 
> Paul Davis wrote:
> >>Various kludgey fixes for this brokenness have
> worked for other 
> >>packages.  export LDFLAGS="-L/usr/local/lib"
> worked for gedit, and 
> >>export LD_LIBRARY_PATH=/usr/local/lib worked for
> pango.  But not ggv.  I 
> >>also tried to pass --libdir=/usr/local/lib.  But
> ggv doesn't seem to 
> >>care that I've told it in many ways to look in
> /usr/local/lib; it 
> >>insists on looking in /usr/lib, because the files
> aren't there.
> > 
> > 
> > PKG_CONFIG_PATH
> > 
> > 
> >>CAN SOMEONE PLEASE TELL ME WHY THESE INSTALLERS
> ARE LOOKING IN THE WRONG 
> >>PLACE.  Please.  Please help.  This is so
> frustrating.
> > 
> > 
> > There are (at least) two conventions for where to
> install things in a
> > linux system. When using any given convention, you
> have to take
> > specific, explicit steps to tell the
> compile/install process to also
> > use the other convention when resolving
> dependencies
> > etc. Unfortunately, there is no single step that
> you can take to do
> > this. Instead, you have to use --prefix with
> configure, set
> > PKG_CONFIG_PATH and various other things.
> > 
> > Its basically a total nightmare.
> > 
> > --p
> > 
> > 
> > 
> 
> _______________________________________________
> gtk-list mailing list
> gtk-list gnome org
> http://mail.gnome.org/mailman/listinfo/gtk-list


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com