>> From: "Michael G. Schabert" <mikeride@prez.buf.servtech.com>
>>
>> Hi NetBSDers,
>> One of those programs that I mentioned had the Dec 30 date happened to be
>> ldconfig (gives wrong architecture error). Unfortunately, that one didn't
>> have a working twin in another directory. Which tarball is ldconfig located
>> in so I can reinstall? Many programs are giving me the shared object
>> libxxxx.so.6 not found because I don't have a working ldconfig.
>>
>>
>> Also, mail dumped core:
>>
>
>NetBSD/alpha doesn't have and doesn't need ldconfig. If your executables
>can't find their libraries then something is way wrong with the install.

To follow up on this, I just did a tar --unlink -pzxvf base.tgz from the
root level on a freshly downloaded tarball from the  arch/alpha/19980420
snapshot. It too put in the bad Dec 30 binaries that I was talking about.
In particular, there was a /use/libexec/ld.elf_so, which I would assume
would be the new replacement for ld.so, since you mentioned that we're the
first NetBSD port to jump on the elf bandwagon. Unfortunately, it too gave:
./ld.elf_so: Exec format error. Wrong Architecture.

Also, on looking at my daily output, I see:
Possible core dumps:
/shutdown.core
/getty.core

so there's definitely something screwy. This week, I'll be getting much
more RAM (twin 32 MB SIMMs), although I allocated about 200 MB to swap,
which should more than make up for my paltry 24 MB currently.

The machine is doing the NAT no problem, & qpopper and sendmail are
working, so I'm not in great need, but it'd be nice to get some packages in
that keep whining about not being able to find shared objects.



Thank you again for all your time,
Mike Schabert

Bikers don't *DO* taglines.