From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 2551] New: [PATCH] native toolchain in the target filesystem fails
Date: Fri, 10 Sep 2010 12:51:58 +0000 (UTC) [thread overview]
Message-ID: <bug-2551-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=2551
Summary: [PATCH] native toolchain in the target filesystem
fails
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: arpinf at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 2449
--> https://bugs.busybox.net/attachment.cgi?id=2449
Patch to fix native toolchain in target filesystem
Buildroot version: 2010.08
Host: x86_64
Target: i686
Selecting:
Package Selection for the target --->
Development tools --->
[*] native toolchain in the target filesystem
Fails with:
mkdir -p /home/illuminate/buildroot-2010.08/output/toolchain/gcc-4.4.4-final
touch
/home/illuminate/buildroot-2010.08/output/build/gcc-4.4.4-target/.prepared
touch: cannot touch
`/home/illuminate/buildroot-2010.08/output/build/gcc-4.4.4-target/.prepared':
No such file or directory
make: ***
[/home/illuminate/buildroot-2010.08/output/build/gcc-4.4.4-target/.prepared]
Error 1
Cause:
Creating the .prepared file in a missing directory.
$(GCC_BUILD_DIR4)/.prepared: $(STAMP_DIR)/gcc_libs_target_installed
$(GCC_TARGET_PREREQ)
mkdir -p $(GCC_BUILD_DIR3)
fixed by changing $(GCC_BUILD_DIR3) to $(GCC_BUILD_DIR4)
Included fix in the patch.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2010-09-10 12:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 12:51 bugzilla at busybox.net [this message]
2010-10-15 14:13 ` [Buildroot] [Bug 2551] [PATCH] native toolchain in the target filesystem fails bugzilla at busybox.net
2011-02-02 15:16 ` 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=bug-2551-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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