From: Micha Holzmann <holzmann@gmx.de>
To: buildroot@busybox.net
Subject: [Buildroot] Problems after building rootfs.i386.ext2
Date: Fri, 14 Mar 2008 15:23:34 +0100 [thread overview]
Message-ID: <20080314142333.GA14688@mail.mhnet.de> (raw)
In-Reply-To: <46a136670803130959n7d6cfcaxf8eb0a78d93acf71@mail.gmail.com>
Hi,
i did what you recommended. I chrooted and tried to mount proc with
several methods.
mount -t proc proc /proc
mount -t proc none /prot
proc was not mounted. mount said, to mount it needs proc mounted. At
this moment mount is a symlink to busybox. I left the chroot and mounted
proc to the proc inside the rootfs and do chroot again. mount without
options shows me infos. But ls -al still stucks until i press CTRL-C.
No change in the behavior.
The second hint you gave me, was to use strace. I activated strace in
the menuconfig. The compiler gives me errors for two lines:
net.c: In function ?printsock?:
net.c:958: error: field ?ll? has incomplete type
net.c:961: error: field ?nl? has incomplete type
make[2]: *** [net.o] Fehler 1
In this case i have no strace which runs inside the chroot.
I tried to build buildroot the last two weeks over 30+ times.
Now i am running out of ideas what to do. :-)
May you have any further idea(s)?
Quoting John Voltz:
> I think when you chroot you need to remount /proc. That can cause weird
> problems like you describe. Also try using strace on commands that fail or
> freeze up. This can be very enlightening (or confusing). You might not even
> be able to chroot into it since you are using uClibc instead of glibc. I
> don't know for sure. Does anyone else?
>
> John Voltz
Best regards,
Micha Holzmann
next prev parent reply other threads:[~2008-03-14 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 16:04 [Buildroot] Problems after building rootfs.i386.ext2 Micha Holzmann
2008-03-13 16:59 ` John Voltz
2008-03-14 14:23 ` Micha Holzmann [this message]
2008-03-14 16:14 ` John Voltz
2008-04-06 10:42 ` Micha Holzmann
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=20080314142333.GA14688@mail.mhnet.de \
--to=holzmann@gmx.de \
--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