Re: Aha! libpng error is the root of my problems; still need help

On Tue, 5 Jan 1999, Gleef wrote:

> That is normal.  A shared library is generally not linked to many other
> libraries, counting instead on the application to supply the appropriate
> library links to resolve the unresolved symbols.  I would be surprised if
> the libraries linked to any more than and /lib/

Usually, yeah, but since 'ldd /usr/lib/', for instance,
gives me: => /usr/lib/ (0x4010b000) => /usr/lib/ (0x4010e000) => /lib/ (0x4012d000) => /usr/X11R6/lib/ (0x40130000) => /usr/X11R6/lib/ (0x4013d000) => /lib/ (0x401e1000) => /lib/ (0x401fa000)
        /lib/ => /lib/ (0x2aaaa000)
I don't take anything for granted with the byzantine interdependancy that is
gnome....  ;-)

> This is probably your problem.  There have been many systems (particularly
> Alphas, but not exclusivly as I understand) with problems with libpng
> 1.0.2.  I suggest you downgrade to libpng 1.0.1.

Hrmn.  I'd thought I'd been using the RH-5.x libpng-1.0.1 RPM all this time,
and just upgraded to try to fix that, but deinstalling all png-related stuff
and reinstalling libpng-*.1.0.1.rpm from the FTP site made it work.  Weird.


Also thanks to Mark Stuermer and Mike Hall for the similar input.  (*whew)
Now I can get around to compiling gnome-core, _finally_.

> Also, when you compiled from source, where did you install it?  Most
> libraries compiled from source go in /usr/local/lib, but convertrgb is
> looking in /usr/lib.

For some long-forgotten reason, I got in the habit of doing --prefix=/usr
for all gnome-related stuff, and so /usr/lib is the correct place....

R Pickett                Look around you. This is what the world      looks like at the end of the millenium.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]