From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 3169] New: python patch has typo, aborts build in scenario
Date: Fri, 28 Jan 2011 20:36:41 +0000 (UTC) [thread overview]
Message-ID: <bug-3169-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=3169
Summary: python patch has typo, aborts build in scenario
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: markw at digi.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 2899
--> https://bugs.busybox.net/attachment.cgi?id=2899
Proposed patch to python patch 005
Pulled from git repository, CHANGES says: 2011-02, not yet released.
python package patch file python-2.7-005-staging-headers-libs.patch has typo in
modules_lib_dirs section, causing build abort if PYTHON_MODULES_LIB is not
specified during build.
+ try:
+ modules_lib_dirs = os.environ["PYTHON_MODULES_LIB"].split()
+ except KeyError:
+ modules_include_dirs = ['/usr/lib']
modules_include_dirs should be modules_lib_dirs:
+ modules_lib_dirs = ['/usr/lib']
Proposed patch to patch is attached, or you could replace existing patch. No
attribution is necessary.
Thanks.
Mark Wickham
Digi International
--
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:[~2011-01-28 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 20:36 bugzilla at busybox.net [this message]
2011-01-29 8:54 ` [Buildroot] [Bug 3169] python patch has typo, aborts build in scenario bugzilla at busybox.net
2011-02-04 18:48 ` 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-3169-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