Skip site navigation (1)Skip section navigation (2)
Date:      27 Nov 2001 09:51:35 +0100
From:      Simon J Mudd <sjmudd@pobox.com>
To:        questions@freebsd.org
Subject:   Re: gv port builds but fails - needing libpng.so.4 (?)
Message-ID:  <86k7wck354.fsf@unicorn.ea4els.ampr.org>
In-Reply-To: erahmig@minn.net's message of "Tue, 27 Nov 2001 04:13:39 %2B0000 (UTC)"
References:  <Pine.LNX.4.33.0111251130400.13547-100000@phoenix.ea4els.ampr.org> <3C02BE71.26378.46004AC@localhost>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Eric,

erahmig@minn.net ("Eric Rahmig") writes:

> I haven't seen any replies to your email so I'll give you my input in 
> the hopes it may be helpful.

Thanks, although looking down at your answer our problems are really
rather different.  I seem to have installed and upgraded packages
in such a way that I've left my system rather "unstable".

> I recently experienced a similar problem. I no longer remember the 
> exact order of events leading up to the problem. I do remember that 
> one of the things I did was to install the gv port.
> 
> The message I was getting was:
> /usr/libexec/ld-elf.so.1: Shared object "libpng.so.5" not found
> 
> I double checked /usr/local/lib and, sure enough, libpng.so.5 was 
> there. The problem seemed to be limited to printing postscript (via 
> gs and magicfilter in my case). Text printed just fine.
> 
> It turns out that somehow the permissions on the /var/run directory
> had been changed from 755 to 750. Since gs runs as 
> daemon:daemon when invoked from an lpd input filter the dynamic 
> loader was unable to read the "hints" files in /var/run and so printed
> the "libpng.so.5 not found" message.
> 
> I figured this out by modifying the lpd input filter. Instead of having it
> invoke gs directly I had it call a shell script. The script used the 
> truss command to run gs and print all the system calls it made.
> By scanning this output I was able to see a "permission denied"
> error when trying to read the "hints" files in /var/run.
> 
> Once I did chmod 755 /var/run postscript printing started working 
> again.

That's interesting: I'm running -STABLE and my /var/run has the
following permissions:

drwxr-xr-x  3 root  wheel  512 27 nov 03:04 /var/run

I assume these permissions are correct and wonder how you managed to
modify your permissions.

My situation is quite different: I've been playing with FreeBSD now
for about 18months, installing packages and ports and stuff like that.
I'd somehow managed to upgrade a dependent package (libpng) so that
the package which depended on it (gv) didn't work.

If you've been following my comments about this, I was being a little
critical about how easy it is to do this, when I would have preferred
a little bit of warning.

Kris and Mike both seem convinced that I should be allowed to shoot
myself in the foot, and that a safety catch is not required.

So it comes down to different filosophies, different experiencies with
package managers on other Oses, or maybe that the documentation is
not careful enough in explaining these potential pitfalls.

Simon
--
Simon J Mudd,   Tel: +34-91-408 4878,  Mobile: +34-605-085 219
Madrid, Spain.  email: sjmudd@pobox.com,  Postfix RPM Packager

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86k7wck354.fsf>