From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1651] New: Build fail caused by ccache in module-init-tools
Date: Thu, 29 Apr 2010 04:28:29 +0000 (UTC) [thread overview]
Message-ID: <bug-1651-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=1651
Summary: Build fail caused by ccache in module-init-tools
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P4
Component: Outdated package
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: mjd-busybox.net at afork.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
I am having problems with the latest buildroot. If I take a stock buildroot
checkout from git, run make menuconfig, then save and make, it compiles. If I
then run make menuconfig, choose Kernel -> Kernel type -> linux (same version
as Linux headers), then do a make, the build fails.
The build fails when it tries to compile module-init-tools. The makefiles call
/usr/lib/ccache/gcc, which fails saying "/usr/bin/ld: cannot find -lc". Please
see attached build log.
--
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-04-29 4:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 4:28 bugzilla at busybox.net [this message]
2010-04-29 4:29 ` [Buildroot] [Bug 1651] Build fail caused by ccache in module-init-tools bugzilla at busybox.net
2010-04-29 6:14 ` bugzilla at busybox.net
2010-04-30 8:07 ` bugzilla at busybox.net
2010-04-30 10:05 ` bugzilla at busybox.net
2010-04-30 10:06 ` bugzilla at busybox.net
2010-05-12 0:17 ` bugzilla at busybox.net
2010-06-24 10:36 ` bugzilla at busybox.net
2010-07-27 2:09 ` bugzilla at busybox.net
2010-07-27 5:34 ` bugzilla at busybox.net
2010-12-14 11:05 ` 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-1651-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