From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1999] New: Typo in path checking
Date: Wed, 9 Jun 2010 09:52:54 +0000 (UTC) [thread overview]
Message-ID: <bug-1999-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=1999
Summary: Typo in path checking
Product: buildroot
Version: unspecified
Platform: Other
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: nick at leverton.org
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 1987
--> https://bugs.busybox.net/attachment.cgi?id=1987
Correct variable case in CWD path check.
Following applies to version 2010.05 but it's not in the BZ version list yet.
Trivial typo in toolchain/dependencies/dependencies.sh means that check for
having CWD in patch can fail to detect it. Attached patch should fix this.
Nick
--
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-06-09 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 9:52 bugzilla at busybox.net [this message]
2010-06-09 10:06 ` [Buildroot] [Bug 1999] Typo in path checking 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-1999-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