From: Ralf Baechle <ralf@oss.sgi.com>
To: Pete Popov <ppopov@mvista.com>
Cc: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: FATAL: cannot determine library version
Date: Sat, 28 Oct 2000 15:18:09 +0200 [thread overview]
Message-ID: <20001028151809.A7138@bacchus.dhis.org> (raw)
In-Reply-To: <39F9B924.97AF7A4@mvista.com>; from ppopov@mvista.com on Fri, Oct 27, 2000 at 10:19:32AM -0700
On Fri, Oct 27, 2000 at 10:19:32AM -0700, Pete Popov wrote:
> I've got a big endian kernel running for a new embedded board, and it
> mounts the root fs over nfs. I'm using the simple-0.2b packages as the
> root fs. At some point after /bin/sh is loaded, I get the following
> error:
>
> FATAL: cannot determine library version
>
> The same root file system is fine on my Indigo2.
Seems your kernel is foobared. On startup libc is trying to determine
the kernel version but both using uname and /proc/sys/kernel/osrelease
fail for some reason.
Ralf
next prev parent reply other threads:[~2000-10-28 22:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-27 17:19 FATAL: cannot determine library version Pete Popov
2000-10-28 13:18 ` Ralf Baechle [this message]
2000-10-30 22:12 ` Pete Popov
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=20001028151809.A7138@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=linux-mips@oss.sgi.com \
--cc=ppopov@mvista.com \
/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