All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Chertov <rchertov@cs.ucsb.edu>
To: buildroot@busybox.net
Subject: [Buildroot] busybox question
Date: Tue, 27 Oct 2009 21:25:41 -0700	[thread overview]
Message-ID: <4AE7C7C5.8090001@cs.ucsb.edu> (raw)
In-Reply-To: <20091027211438.BEC2B7773A@busybox.osuosl.org>

Hello,

I have an ARM920T board that I am trying to get going with buildroot and
uClibc.  I managed to compile the kernel, and it boots up to the point
where the login must happen.  Nothing happens at that point.  However,
the machine runs as I can ping it.  I have tried to init=/bin/sh
init=/bin/ethtool, but I did not get any output to indicate that
something started.

I have the following question.  I can build the default image on the
board (Debian 2.4, glibc) and mount the buildroot root fs over NFS.
However, if I try to execute any program, I get the following errors:

root at ts7000:bin# ./busybox
-bash: ./busybox: No such file or directory

I would expect that at least the program would start and then an error
would occur due to the fact that uClibc is not present.  I am correct in
assuming this?  I am trying to debug if I screwed the cross compiling
(although Linux kernel boots), or if there is a problem with the init
process.


I would appreciate some insight into this issue.

Thanks,

Roman

  reply	other threads:[~2009-10-28  4:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27 21:12 [Buildroot] [git commit master] synergy: needs C++ support Peter Korsgaard
2009-10-28  4:25 ` Roman Chertov [this message]
2009-10-28 10:13   ` [Buildroot] busybox question Peter Korsgaard
2009-10-28 16:26     ` Roman Chertov
2009-10-28 16:46       ` Emmanuel Riou
2009-10-28 19:35         ` Roman Chertov
2009-10-28 20:37           ` Peter Korsgaard
2009-10-28 20:51             ` Roman Chertov
2009-10-28 21:00               ` Peter Korsgaard
2009-10-29 16:10                 ` Roman Chertov
2009-10-28 19:36       ` Peter Korsgaard

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=4AE7C7C5.8090001@cs.ucsb.edu \
    --to=rchertov@cs.ucsb.edu \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.