Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Micha Holzmann <holzmann@gmx.de>
To: buildroot@busybox.net
Subject: [Buildroot] Problems after building rootfs.i386.ext2
Date: Thu, 13 Mar 2008 17:04:11 +0100	[thread overview]
Message-ID: <20080313160410.GA13136@mail.mhnet.de> (raw)

Hello all,

after the rootfs ist built, i discoverd some problems which i can not
solve by myself.


Here are some infos about my environment:

It is a Thinkpad R60 Laptop with Core2 Duo and 2GiB RAM.
Operating system is Kubuntu 7.10 and this is the way i
tried to make my own buildroot.
I do not work as root (except the loop mount and chroot).
I set LANG to C before starting the whole building.


 svn co svn://uclibc.org/trunk/buildroot
 cd buildroot
 make menuconfig


These are the main settings i choose:

Target Architecture (i386)
Target Architecture Variant (i386)
Target filesystem options EXT2
Linux Kernel Version (Linux 2.6.24)

The other settings are left on standard settings.


The run make

Aborting.  'target/device/x86/i386/kernel-patches-2.6.24/' is not a directory.
make: *** [/home/development/uclibc/buildroot/project_build_i386/uclibc/linux-2.6.24/.patched] Error 1


I made the dir and started make again

 mkdir -p target/device/x86/i386/kernel-patches-2.6.24/

You should create a .config for your kernel
and install it as target/device/x86/i386/linux-2.6.24.config

OK, jump to the dir and...

 pushd project_build_i386/uclibc/linux-2.6.24
 cp /boot/config-2.6.22-14-386 .config
 make oldconfig
 popd
 cp project_build_i386/uclibc/linux-2.6.24/.config
 target/device/x86/i386/linux-2.6.24.config
 make

make: *** No rule to make target `package/busybox/busybox-1.9.0.config', needed by /home/development/uclibc/buildroot/project_build_i386/uclibc/busybox-1.9.1/.configured'.
Stop.

OK, jump to the dir and...

 pushd project_build_i386/uclibc/busybox-1.9.1
 make menuconfig
 popd
 cp project_build_i386/uclibc/busybox-1.9.1/.config
 package/busybox/busybox-1.9.0.config
 make


After a long time, the rootfs was built. I run make menuconfig again and
switch on
[*] native toolchain in the target filesystem
[*] make

and built the rootfs again.


I mount it at loop device and chroot in to it. I could chdir and run some programs.
ls produces the known output but ls -al said:

# ls -al

rupt (core dumped)

and ls -l keep stcuking without any output as long as i do not hit CTRL-C.

The next i tried to compile the gawk sources. In another console (not
chroot) i extract the sources into the mounted rootfs and run
./configure --help.

This stucks also.


I searched using google and the list archives but could not find an
answer. What have i did wrong? I also read the docs/buildrott.html.

If anyone is willing to give me a hint or a link, it is very
appreceated.


Best regards and thanks in adcance,
Micha Holzmann

-- 
GPG Public-Key: send a Mail with Subject: GPG-KEY
Key fingerprint = 6FEF 16C5 17EF 9573 892B  D810 66B9 8FBD 0EBA 820F

             reply	other threads:[~2008-03-13 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13 16:04 Micha Holzmann [this message]
2008-03-13 16:59 ` [Buildroot] Problems after building rootfs.i386.ext2 John Voltz
2008-03-14 14:23   ` Micha Holzmann
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=20080313160410.GA13136@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