Hello!

I've been preparing some FreeBSD boxes for the new project going on, and
when I already created all needed images, and cloned my second box, I
encountered this problem:

$ man whatever

it yields

/usr/libexec/ld-elf.so.1: Cannot open "/usr/lib/libz.so.2"

Which is very strange :-(

When I say

$ ldd `which man`

I get

/usr/bin/man:
        libz.so.2 => not found (0x0)
        libc.so.4 => not found (0x0)

But (!) when I say

$ ldd `which fetch`

I get what I normally should:

/usr/bin/fetch:
        libfetch.so.2 => /usr/lib//libfetch.so.2 (0x2806a000)
        libc.so.4 => /usr/lib//libc.so.4 (0x28074000)

Note that both man and fetch are linked against libc.so.4, but it does not
find it in case of man.

Grepping ldconfig output yields:

$ ldconfig -r|grep libz
       53:-lz.2 => /usr/lib/libz.so.2

Frankly, I don't quite understand what happened.  Manuals *used* to work,
that's for sure.

I tought of corrupted libraries, but all MD5 sums matched what they
should.  I even reinstalled man (cd /usr/src/gnu/usr.bin/man && make all
install) -- didn't help.  I removed all hints from /var/run and remade
them, no effect.

What surprised me as well, was:

$ touch /usr/libexec/ld-elf.so.1
touch: ld-elf.so.1: Text file busy

What this `text` thing is about?

I'd really appreciate this problem solved, and many thanks in advance for
any help with regard to this.

Oh yeah, it's FreeBSD-4.2-STABLE snapshot from 20010402, kernel/world made
on SMP box (p3x2).

Any additional information is available upon request.

--
        WBR
        Alexey

P.S.  Sorry for x-posting, I was not quite sure where this letter should
have really went.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Reply via email to