From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] at91rm9200df/busybox-1.6.1.config: No such file or directory
Date: Thu, 09 Aug 2007 22:13:13 +0300 [thread overview]
Message-ID: <46BB6749.3020301@promwad.com> (raw)
Hello,
Ulf, possibly for your attention:
busybox-1.6.1.config missing when trying to build for at91rm9200df:
bzcat /downloads/busybox-1.6.1.tar.bz2 | tar -C /root/buildroot/project_build_arm/uclibc -xf -
tar: Read 5632 bytes from -
# Allow busybox patches.
toolchain/patch-kernel.sh /root/buildroot/project_build_arm/uclibc/busybox-1.6.1 package/busybox busybox-1.6.1-\*.patch
touch /root/buildroot/project_build_arm/uclibc/busybox-1.6.1/.unpacked
cp -f target/device/Atmel/at91rm9200df/busybox-1.6.1.config /root/buildroot/project_build_arm/uclibc/busybox-1.6.1/.config
cp: cannot stat `target/device/Atmel/at91rm9200df/busybox-1.6.1.config': No such file or directory
make: *** [/root/buildroot/project_build_arm/uclibc/busybox-1.6.1/.configured] Error 1
The patch in the attachment fixes the problem.
Best regards,
Ivan
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch.diff
Url: http://busybox.net/lists/buildroot/attachments/20070809/c4788e73/attachment-0001.diff
reply other threads:[~2007-08-09 19:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46BB6749.3020301@promwad.com \
--to=ivan.kuten@promwad.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