From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5360] New: buildroot fails when building "host-libglib2 2.30.2 Building"
Date: Fri, 13 Jul 2012 18:21:34 +0000 (UTC) [thread overview]
Message-ID: <bug-5360-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=5360
Summary: buildroot fails when building "host-libglib2 2.30.2
Building"
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: anton at fit.com.ru
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 4406
--> https://bugs.busybox.net/attachment.cgi?id=4406
configuration file buildroot
Hello,
I have attached the config file that reproduces this bug (basically i think to
reproduce this bug what you need to do is try to build the libglib2).
The following final error is given:
SyntaxErrorSyntaxError: : Non-ASCII character '\xd0' in file
../../gio/gdbus-2.0/codegen/gdbus-codegen on line 36, but no encoding declared;
see http://www.python.org/peps/pep-0263.html for detailsNon-ASCII character
'\xd0' in file ../../gio/gdbus-2.0/codegen/gdbus-codegen on line 36, but no
encoding declared; see http://www.python.org/peps/pep-0263.html for details
Anton
PS
This is a very strange bug.
Honestly i was expecting that such standard libraries are building correctly by
now.
--
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-07-13 18:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 18:21 bugzilla at busybox.net [this message]
2012-07-13 20:52 ` [Buildroot] [Bug 5360] buildroot fails when building "host-libglib2 2.30.2 Building" bugzilla at busybox.net
2012-07-13 22:42 ` bugzilla at busybox.net
2012-07-14 8:10 ` bugzilla at busybox.net
2012-07-14 8:12 ` bugzilla at busybox.net
2012-07-14 10:20 ` bugzilla at busybox.net
2012-07-14 12:51 ` bugzilla at busybox.net
2012-07-14 15:01 ` bugzilla at busybox.net
2012-07-14 15:02 ` bugzilla at busybox.net
2012-07-14 15:23 ` bugzilla at busybox.net
2012-07-15 16:20 ` bugzilla at busybox.net
2012-07-15 16:21 ` bugzilla at busybox.net
2012-07-15 17:10 ` bugzilla at busybox.net
2012-07-16 5:12 ` bugzilla at busybox.net
2012-07-16 7:17 ` bugzilla at busybox.net
2012-07-16 8:44 ` bugzilla at busybox.net
2012-07-16 8:51 ` bugzilla at busybox.net
2012-07-16 17:05 ` bugzilla at busybox.net
2012-07-18 20:44 ` bugzilla at busybox.net
2012-08-21 12:00 ` 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-5360-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