From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] cannot log to my build root
Date: Tue, 14 Dec 2010 17:00:44 +0100 [thread overview]
Message-ID: <20101214170044.674c2d0d@surf> (raw)
In-Reply-To: <4D07922D.9090309@carallon.com>
On Tue, 14 Dec 2010 15:50:05 +0000
William Wagner <will_wagner@carallon.com> wrote:
> I have also seen this. In my case the problem was that I had built an
> eglibc toolchain that had configured too much out (I think it was option
> OPTION_EGLIBC_NIS). Busybox built fine, only login as root failed.
>
> Never got around to debugging it as much faster just to change my
> toolchain to include the necessary option.
Yes, but in his case, he is using a well-known CodeSourcery toolchain,
which I also tested, and which works.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2010-12-14 16:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 13:06 [Buildroot] cannot log to my build root Diego Iastrubni
2010-12-14 13:25 ` Thomas Petazzoni
2010-12-14 13:39 ` Diego Iastrubni
2010-12-14 14:05 ` Thomas Petazzoni
2010-12-14 14:38 ` Diego Iastrubni
2010-12-14 14:42 ` Thomas Petazzoni
2010-12-14 14:54 ` Diego Iastrubni
2010-12-14 15:05 ` Thomas Petazzoni
2010-12-14 15:28 ` Diego Iastrubni
2010-12-14 15:37 ` Thomas Petazzoni
2010-12-14 15:56 ` Diego Iastrubni
2010-12-14 16:00 ` Thomas Petazzoni
2010-12-14 15:50 ` William Wagner
2010-12-14 16:00 ` Thomas Petazzoni [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=20101214170044.674c2d0d@surf \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox