From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 219] New: Toolchain build fails on m4
Date: Thu, 26 Mar 2009 18:19:54 +0000 (UTC) [thread overview]
Message-ID: <bug-219-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=219
Host: Linux archlinux 2.6.28-ARCH #1 SMP PREEMPT Sun Feb 8
10:13:45 UTC 2009 i686 Intel(R) Xeon(R) CPU X3350 @
2.66GHz GenuineIntel GNU/Linux
Target: x86-64
Build: buildroot-20090326
Summary: Toolchain build fails on m4
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: critical
Priority: P2
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: info at je-eigen-domein.nl
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Buildroot fails building the toolchain:
===
# Make sure we have 'cc'.
if [ ! -e /home/max/buildroot/project_build_x86_64/maxtest/root/usr/bin/cc ];
then \
ln -snf gcc
/home/max/buildroot/project_build_x86_64/maxtest/root/usr/bin/cc; \
fi
# These are in /lib, so...
#rm -rf
/home/max/buildroot/project_build_x86_64/maxtest/root/usr/lib/libgcc_s*.so*
touch -c /home/max/buildroot/project_build_x86_64/maxtest/root/usr/bin/gcc
make: *** No rule to make target `/home/max/buildroot/dl/m4-1.4.9.tar.bz2',
needed by `/home/max/buildroot/build_x86_64/stamps/host_m4_unpacked'. Stop.
===
--
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:[~2009-03-26 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 18:19 bugzilla at busybox.net [this message]
2009-03-26 19:21 ` [Buildroot] [Bug 219] Toolchain build fails on m4 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-219-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.