linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Brian Boerner <bboerner@yahoo.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: libc.so.6: cannot open shared object file: No such file or directory
Date: Wed, 11 Jul 2001 15:58:01 +0200	[thread overview]
Message-ID: <20010711135806.51F3F10DC8@denx.denx.de> (raw)
In-Reply-To: Your message of "Wed, 11 Jul 2001 06:45:20 PDT." <20010711134520.31259.qmail@web14202.mail.yahoo.com>


In message <20010711134520.31259.qmail@web14202.mail.yahoo.com> you wrote:
>
> IBM Walnut 405GP. Linux is MontaVista
...
> I did see one post mentioning that you needed a
> symbolic link from the hardhat devkit to /. I was a
> bit unclear on this and didn't see anything about this
> in the mvista cdk documentation. I may have missed it,
> anything is possible at this point.
>
> Does anyone have any idea why init is being killed
> off? It complains libc.so.6 isn't being found? It's
> certainly in the ramdisk. I'm sure folks have run into
> this before.

See http://www.denx.de/tips+tricks-en.html#libpath

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
"He only drinks when he gets depressed." "Why does he get depressed?"
"Sometimes it's because he hasn't had a drink."
                                     - Terry Pratchett, _Men at Arms_

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-07-11 13:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-11 13:45 libc.so.6: cannot open shared object file: No such file or directory Brian Boerner
2001-07-11 13:58 ` Wolfgang Denk [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010711135806.51F3F10DC8@denx.denx.de \
    --to=wd@denx.de \
    --cc=bboerner@yahoo.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).