From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Cc: "Corey" <corey@bitworthy.net>
Subject: Re: [gentoo-embedded] unable to chroot
Date: Fri, 17 Nov 2006 17:15:26 -0500 [thread overview]
Message-ID: <200611171715.27052.vapier@gentoo.org> (raw)
In-Reply-To: <200611171435.44844.corey@bitworthy.net>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
On Friday 17 November 2006 16:35, Corey wrote:
> scanner gentoo # ./bin/bash --version
> GNU bash, version 3.1.17(1)-release (i686-pc-linux-gnu)
> Copyright (C) 2005 Free Software Foundation, Inc.
> scanner gentoo # chroot /mnt/gentoo/ /bin/bash
> chroot: cannot run command `/bin/bash': No such file or directory
assuming / is glibc and /mnt/gentoo is uclibc, this looks like the bin/bash is
incorrectly linked against glibc
try running `readelf -d bin/bash` and make sure it is linked against uClibc
libs
-mike
[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2006-11-17 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 21:35 [gentoo-embedded] unable to chroot Corey
2006-11-17 22:15 ` Mike Frysinger [this message]
2006-11-17 22:45 ` Hanni Ali
2006-11-18 0:10 ` Corey
2006-11-18 0:08 ` Corey
2006-11-18 6:35 ` Corey
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=200611171715.27052.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=corey@bitworthy.net \
--cc=gentoo-embedded@lists.gentoo.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