From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7802] New: host-python build hangs compiling getbuildinfo.o
Date: Fri, 16 Jan 2015 15:11:08 +0000 (UTC) [thread overview]
Message-ID: <bug-7802-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=7802
Summary: host-python build hangs compiling getbuildinfo.o
Product: buildroot
Version: 2014.11
Platform: PC
OS/Version: Linux
Status: NEW
Severity: blocker
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: codehero at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 5810
--> https://bugs.busybox.net/attachment.cgi?id=5810
kos_tom's patch to disable hg and svn build info tags
When building the host python, hg or svn is invoked to create build info tags.
This can result in a socket hang, blocking compilation from completion.
The solution, as determined by kos_tom on #buildroot (THANK YOU), was to
disable hg and svn from python's automake.
--
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:[~2015-01-16 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 15:11 bugzilla at busybox.net [this message]
2015-01-16 21:32 ` [Buildroot] [Bug 7802] host-python build hangs compiling getbuildinfo.o bugzilla at busybox.net
2015-04-06 3:30 ` bugzilla at busybox.net
2015-04-16 9:07 ` bugzilla at busybox.net
2015-04-16 9:07 ` bugzilla at busybox.net
2016-08-31 21:19 ` bugzilla at busybox.net
2016-09-18 15:13 ` 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-7802-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