From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2018.05-rc3 released
Date: Wed, 30 May 2018 18:15:03 +0200 [thread overview]
Message-ID: <87efht2k8o.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180530180026.77e1dfac@windsurf.home> (Thomas Petazzoni's message of "Wed, 30 May 2018 18:00:26 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
Hi,
>> Ok, interesting. Enabling python3 for the target means that our host
>> python becomes python3,
> Yes that is expected.
Yes, but that could conceptually explain why Mike sees a difference in
behaviour.
>> > The Linux distribution/version I am building on is Fedora Red Hat 25
>> > ...
>>
>> > [mike at modron ~]$ uname -a
>> > Linux modron 4.9.14-200.fc25.x86_64 #1 SMP Mon Mar 13 19:26:40 UTC 2017
>> > x86_64 x86_64 x86_64 GNU/Linux
>>
>> Ok, I'm on Debian. Thomas, you are using Fedora now, right? Can you give
>> ca-certificates a try?
> It builds fine here: http://code.bulix.org/092xcg-342074?raw
Thanks, just like on my machine and the autobuilders.
Mike, there must be something odd going on with your machine. I'm afraid
you will have to debug it further yourself. Maybe try running
certdata2pem.py manually?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-05-30 16:15 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 [this message]
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=87efht2k8o.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