[Buildroot] Buildroot 2018.05-rc3 released
busybox_mail at rovoreed.com
Thu May 31 18:30:04 UTC 2018
On Thu, 2018-05-31 at 17:26 +0200, Thomas Petazzoni wrote:
> 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-
> 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.
More information about the buildroot