From: Mike Davies <busybox_mail@rovoreed.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2018.05-rc3 released
Date: Thu, 31 May 2018 19:30:04 +0100 [thread overview]
Message-ID: <1527791404.2065.8.camel@rovoreed.com> (raw)
In-Reply-To: <20180531172600.3cc0568e@windsurf>
On Thu, 2018-05-31 at 17:26 +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Thu, 31 May 2018 15:52:49 +0100, Mike Davies wrote:
>
> > OK, well, it seems to be that when host_python is being configured,
> > the
> > configure script has not got the option...
> >
> > --enable-unicode=ucs4
> >
> > and it's not got that because python.mk uses a symbol
> > BR2_PACKAGE_PYTHON_UCS4 to decide whether to add that option to
> > HOST_PYTHON_CONF_OPTS
> >
> > I do not have?BR2_PACKAGE_PYTHON_UCS4 in my .config file.
> >
> > [mike at modron buildroot-2018.05-rc3]$ cat .config | grep PYTHON
> > # BR2_PACKAGE_MICROPYTHON is not set
> > # BR2_PACKAGE_HOST_PYTHON_CYTHON is not set
> > # BR2_PACKAGE_HOST_PYTHON_LXML is not set
> > # BR2_PACKAGE_HOST_PYTHON_SIX is not set
> > # BR2_PACKAGE_HOST_PYTHON_XLRD is not set
> > # BR2_PACKAGE_PYTHON_PYXML is not set
> > [mike at modron buildroot-2018.05-rc3]$?
> >
> > I do not know the implications of simply moving --enable-
> > unicode=ucs4
> > to the list of HOST_PYTHON_CONF_OPTS at the start of python.mk.
>
> But why would UCS4 support be required for you to build ca-
> certificates
> and not on other systems ?
>
> My test build had BR2_PACKAGE_PYTHON_UCS4 disabled, so
> --enable-unicode=ucs4 was also not passed when building host-python.
>
Why it builds OK for others and not me, then, sorry, I don't know.
When I build ca-certificates I saw that host-python was complaining
about undefined symbol: PyUnicodeUCS2_AsEncodedString, so I fiddled
about with the parameters to the host python configure script, noted
that if I force the host python configure with --enable-unicode=ucs4
then it works. If I change that to --enable-unicode=ucs2 or --enable-
unicode then it fails the same.
I'm not a Python programmer. This PC does not have Python on it at all,
and it only gets dragged in by buildroot to build ca-certificates.
Maybe that is something to do with it.
Let's not waste any more time on it.
Mike
next prev parent reply other threads:[~2018-05-31 18:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 6:44 [Buildroot] Buildroot 2018.05-rc3 released Peter Korsgaard
2018-05-29 13:18 ` Mike Davies
2018-05-29 14:58 ` Peter Korsgaard
[not found] ` <1527615682.2053.4.camel@rovoreed.com>
2018-05-29 18:47 ` Peter Korsgaard
[not found] ` <1527674917.2072.2.camel@rovoreed.com>
2018-05-30 15:42 ` Peter Korsgaard
2018-05-30 16:00 ` Thomas Petazzoni
2018-05-30 16:12 ` Romain Naour
2018-05-30 16:15 ` Peter Korsgaard
2018-05-31 7:56 ` Mike Davies
2018-05-31 14:52 ` Mike Davies
2018-05-31 15:26 ` Thomas Petazzoni
2018-05-31 18:30 ` Mike Davies [this message]
2018-05-31 20:18 ` Arnout Vandecappelle
2018-06-04 18:51 ` Mike Davies
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=1527791404.2065.8.camel@rovoreed.com \
--to=busybox_mail@rovoreed.com \
--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