From: Martin Hicks <mort@bork.org>
To: Aman <aman@mistralsoftware.com>
Cc: Mark Hatle <fray@mvista.com>,
linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Serial Console Login Fails
Date: Wed, 23 Apr 2003 09:59:41 -0400 [thread overview]
Message-ID: <20030423135941.GK553@bork.org> (raw)
In-Reply-To: <001701c3099e$c1f900f0$370da8c0@aman>
On Wed, Apr 23, 2003 at 07:16:35PM +0530, Aman wrote:
> Hi Martin
>
> I have the etc/securetty file with entry ttyS0. Actually I cant see the log
> messages since the linux boots up and gets struck in the login itself . Is
> there any other way to get the log messages. In my board , I don't have
> network support. So each I time I have to modify the ramdisk image and run
> it. I tried putting in /bin/login, however I getting the following error
> "/bin/login: error while loading shared libraries: cannot open shared object
> file
> : cannot load shared object file: No such file or directory"
> I think the related shared libraries is not there , how to find related
> shared libraries for any file.
You can check which shared libraries are required in order to run an
application with "ldd". There should be a cross version on your host
system with your development kit.
Otherwise, I'd compile login statically (or use busybox or something
similar) to get past this hurdle and get the correct shared libs
installed.
mh
--
Martin Hicks || mort@bork.org || PGP/GnuPG: 0x4C7F2BEE
plato up 5 days, 22:50, 12 users, load average: 0.62, 0.51, 0.55
Great Spirits have always encountered opposition from mediocre minds
-Albert Einstein
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-04-23 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 2:11 Serial Console Login Fails Aman
2003-04-23 12:30 ` Martin Hicks
2003-04-23 12:59 ` Mark Hatle
2003-04-23 13:46 ` Aman
2003-04-23 13:59 ` Martin Hicks [this message]
2003-04-23 14:13 ` Mark Hatle
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=20030423135941.GK553@bork.org \
--to=mort@bork.org \
--cc=aman@mistralsoftware.com \
--cc=fray@mvista.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).