From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5630] New: makefile error with toolchain helpers.mk
Date: Fri, 26 Oct 2012 19:23:50 +0000 (UTC) [thread overview]
Message-ID: <bug-5630-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=5630
Summary: makefile error with toolchain helpers.mk
Product: buildroot
Version: 2012.08
Platform: All
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: gunslnger_ at hotmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
There are a couple errors in toolchain/helpers.mk in the check_glibc function.
First, the strip $1 appears to remove everything, not just the trailing '/'.
Second, the test command has a typo; it references SYSDROOT_DIR instead of
SYSROOT_DIR.
--
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:[~2012-10-26 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 19:23 bugzilla at busybox.net [this message]
2013-10-12 14:26 ` [Buildroot] [Bug 5630] makefile error with toolchain helpers.mk 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-5630-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.