From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6290] New: copying the kernel fails
Date: Sat, 01 Jun 2013 20:40:31 +0200 [thread overview]
Message-ID: <51AA401F.9050301@mind.be> (raw)
In-Reply-To: <bug-6290-163@https.bugs.busybox.net/>
On 29/05/13 08:23, bugzilla at busybox.net wrote:
> https://bugs.busybox.net/show_bug.cgi?id=6290
>
> Summary: copying the kernel fails
> Product: buildroot
> Version: unspecified
> Platform: PC
> OS/Version: Linux
> Status: NEW
> Severity: critical
> Priority: P5
> Component: Other
> AssignedTo: unassigned at buildroot.uclibc.org
> ReportedBy: jungmann0 at gmail.com
> CC: buildroot at uclibc.org
> Estimated Hours: 0.0
>
>
> I want to build a linux system for my arm-based PDA (Intel PXA255 processor).
> The build fails with the following message:
>
> # dtbs moved from arch/RCH/boot to arch/RCH/boot/dts since 3.8-rc1
> cp /home/jakob/Downloads/Buildroot/output/target/boot/
> cp is missing the destination
> ?cp --help? gives more information.
> make: ***
> [/home/jakob/Downloads/Buildroot/output/build/linux-3.7.8/.stamp_target_installed]
> Error 1
Probably BR2_LINUX_KERNEL_CUSTOM_DTS_PATH or
BR2_LINUX_KERNEL_INTREE_DTS_NAME is empty. We should add a check for that.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-06-01 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 6:23 [Buildroot] [Bug 6290] New: copying the kernel fails bugzilla at busybox.net
2013-05-29 19:12 ` [Buildroot] [Bug 6290] " bugzilla at busybox.net
2013-06-01 18:40 ` Arnout Vandecappelle [this message]
2013-11-14 0:07 ` bugzilla at busybox.net
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=51AA401F.9050301@mind.be \
--to=arnout@mind.be \
--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