Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sjhill at realitydiluted.com <sjhill@realitydiluted.com>
To: buildroot@busybox.net
Subject: [Buildroot] Glibc instead of uclibc
Date: Fri, 7 Mar 2008 12:17:53 -0600	[thread overview]
Message-ID: <20080307181753.GB31953@real.realitydiluted.com> (raw)
In-Reply-To: <c05908680803070918k635d6106qa7b4ad5aa5634cea@mail.gmail.com>

On Fri, Mar 07, 2008 at 06:18:52PM +0100, Salvatore Fassi wrote:
> 
> I had been able to compile a complete rootfs with xorg and gtk and to boot
> it, but I had to copy libcrypt, libm and ld-linux.so (with all their links
> etc etc) manually because on my rootfs /lib there was only libc.
> Now the system boots ok...but I can't login!!
> I've tried using "root" with various passwords (also empty one) but I'm
> still not able to log in...
> 
> Am I missing some other libraries? Why do all these libraries weren't copied
> in the rootfs automatically?  :-/
> P.S : For your information...I'm using my linux pc toolchain (fedora core 6)
> as an external toolchain for buildroot.
> 
You are missing the other libraries. Here is what my buildroot config
options look like for my buildroot using an external glibc toolchain:

BR2_TOOLCHAIN_EXTERNAL_LIB_C="libc.so.6"
BR2_TOOLCHAIN_EXTERNAL_LIBS="ld.so.1 libcrypt.so libdl.so libgcc_s.so libm.so libnsl.so libnss_dns.so libnss_files.so libpthread.so libresolv.so librt.so libstdc++.so libutil.so"

The libraries that you do not have which are preventing you from logging
in our 'libnsl.so' and 'libnss_dns.so' and 'libnss_file.so'. Once those
are in your root filesystem, you will be able to login.

-Steve

  reply	other threads:[~2008-03-07 18:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05 15:44 [Buildroot] Glibc instead of uclibc Salvatore Fassi
2008-03-05 16:59 ` sjhill at realitydiluted.com
2008-03-05 17:16   ` Salvatore Fassi
2008-03-05 17:23     ` JS
2008-03-05 17:33       ` Salvatore Fassi
2008-03-06  7:12         ` Emil Krüper
2008-03-06  7:27           ` Salvatore Fassi
2008-03-06  9:25             ` Salvatore Fassi
2008-03-07 17:18               ` Salvatore Fassi
2008-03-07 18:17                 ` sjhill at realitydiluted.com [this message]
2008-03-05 17:23     ` Rex Ashbaugh
2008-03-05 17:27       ` Salvatore Fassi
2008-03-05 17:28     ` sjhill at realitydiluted.com
  -- strict thread matches above, loose matches on Subject: below --
2012-08-03 14:47 [Buildroot] glibc " Zoran Djordjevic

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=20080307181753.GB31953@real.realitydiluted.com \
    --to=sjhill@realitydiluted.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