Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2018.05-rc3 released
Date: Tue, 29 May 2018 16:58:45 +0200	[thread overview]
Message-ID: <87fu2a7bkq.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1527599917.2053.2.camel@rovoreed.com> (Mike Davies's message of "Tue, 29 May 2018 14:18:37 +0100")

>>>>> "Mike" == Mike Davies <busybox_mail@rovoreed.com> writes:

 > ca-certificates fails to build. Though I see there is some discussion
 > on the list, I'm unsure if it is connected to the build failing.
 > My real build needs a lot more stuff, but it can be trimmed down to
 > this for it to fail...

 > tar -xzf /home/mike/Downloads/buildroot-2018.05-rc3.tar.gz
 > cd b*3
 > make raspberrypi3_64_defconfig
 > make menuconfig
 > Target Packages->Libraries->Crypto->CA Certificates
 > make

 > PATH="/home/mike/work/pi/buildroot-2018.05-rc3/output/host/bin:/home/mike/work/pi/buildroot-2018.05-rc3/output/host/sbin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/home/mike/bin:/sbin:/home/mike/.local/bin:/home/mike/bin:/home/mike/bin:/sbin" /usr/bin/make -j9 -C /home/mike/work/pi/buildroot-2018.05-rc3/output/build/ca-certificates-20170717 all
 > for dir in mozilla; do \
 >   /usr/bin/make -C $dir all; \
 > done
 > python certdata2pem.py
 > Traceback (most recent call last):
 >   File "certdata2pem.py", line 23, in <module>
 >     import base64
 >   File "/home/mike/work/pi/buildroot-2018.05-rc3/output/host/lib64/python2.7/base64.py", line 9, in <module>
 >     import struct
 >   File "/home/mike/work/pi/buildroot-2018.05-rc3/output/host/lib64/python2.7/struct.py", line 1, in <module>
 >     from _struct import *
 > ImportError: /home/mike/work/pi/buildroot-2018.05-rc3/output/host/lib64/python2.7/lib-dynload/_struct.so: undefined symbol: PyUnicodeUCS2_AsEncodedString

Hmm, strange. Nothing has really changed to host-python recently. Is
this a new regression since 2018.05-rc2? What host OS are you using?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-05-29 14:58 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 [this message]
     [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
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=87fu2a7bkq.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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