libc.so.6 not found

[Niels Kobschaetzki]

On Mon, Mar 31, 2008 at 3:36 PM, Kris Kennaway <kris at freebsd.org> wrote:
>
> Niels Kobschaetzki wrote:
>  > On Mon, Mar 31, 2008 at 2:21 PM, Kris Kennaway <kris at freebsd.org> wrote:
>  >> Niels Kobschaetzki wrote:
>  >>  > Hi!
>  >>  >
>  >>  > I have here severe problems with installing stuff. I tried to
>  >>  > recompile xemacs 21.4 and got a:
>  >>  > /libexec/ld-elf.so.1: Shared object "libc.so.6" not found, required by
>  >>  > "install-info"
>  >>  > I searched google and it seems that this is from FreeBSD 6 while I am
>  >>  > running 7 and I have only libc.so.7 on my system.
>  >>  > I wondered, tried to compile xemacs 21.5 from the sources and ran into
>  >>  > some other trouble. I figured that I'll do a a cvsup with FreeBSD
>  >>  > 7.0-stable and do a portupgrade -ra to do an upgrade for all packages;
>  >>  > hoping that the trouble wents away and I get some kind of xemacs with
>  >>  > mule-support installed. But the portupgrade ran into some problems
>  >>  > because of a stale dependency (ORBit2-2.14.10 -> libIDL-0.8.9_1
>  >>  > (devel/libIDL).
>  >>  > I want to install now this stale dependency and get the same error:
>  >>  > /libexec/ld-elf.so.1: Shared object "libc.so.6" not found, required by
>  >>  > "install-info"
>  >>  >
>  >>  > Anyone who can help here?
>  >>
>  >>  I guess you missed part of the upgrade steps when you updated to 7.0.
>  >>  The step you missed involved a portupgrade -fa (or -faP) to refresh all
>  >>  of your ports with 7.0 versions to avoid precisely this problem.  You
>  >>  should do that now to repair your system.
>  >
>  > I never upgraded - I did a direct install of 7.0 from downloaded isos.
>
>  That doesn't explain why you have lots of installed 6.x packages.

Well, I do not have any idea neither -- I never touched anything
mentioning FreeBSD 6.x

>  > I found the solution in the meanwhile though.
>  > Just create /etc/libmap.conf and put
>  > libc.so.6           libc.so.7
>  > in it and the problem vanishes
>
>  That is not the solution.

Yeah, pkgdb -F ran through after that w/out any problem, running
portupgrade -ra or portupgrade -fa advices me to do the same again.
Doing that now…last time it took an hour or so…I hope I can go on then
with portupgrade

Right now the system seems to be messed up like in times when I worked
with SuSE-linux and played around with alpha-stuff and forced my way
through the rpm-database…even though I didn't even touch current or
anything below 7 (at least not that I know off) and never worked with
a -f -option (I learned my lessons years ago with force-options)

Niels