From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] defconfig build issues
Date: Sun, 06 May 2018 21:22:06 +0200 [thread overview]
Message-ID: <87muxcpp29.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <5917efea-77e3-e66d-7d2b-b0225f041d4f@mind.be> (Arnout Vandecappelle's message of "Sun, 6 May 2018 17:27:04 +0200")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
> On 06-05-18 15:50, Martin Bark wrote:
>> Hi,
>>
>> On 6 May 2018 at 07:34, Peter Korsgaard <peter@korsgaard.com> wrote:
>>>>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> [snip]
>>> > raspberrypi3_qt5we_defconfig
>>> > ============================
>>>
>>> > Your Buildroot configuration needs a compiler capable of building 32 bits binaries.
>>> > If you're running a Debian/Ubuntu distribution, install the g++-multilib package.
>>> > For other distributions, refer to their documentation.
>>>
>>> > https://gitlab.com/buildroot.org/buildroot/-/jobs/66561791
>>
>> support/docker/Dockerfile already installs g++-multilib but the image
>> buildroot/base:20180205.0730 lacks it. It looks like g++-multilib was
>> added just after the image was created in commit
>> 27d22296927d7e4ec0965f2bdaa272b1e8ea15e7
>>
>> So i think this should already be fixed, you just need to update the
>> buildroot/base image
> Or rather, 12b08c2be639e26ba0983d7dbdb3bddd91355f4c should be backported to
> 2018.02.
Ahh - Committed to 2018.02.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2018-05-06 19:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 19:52 [Buildroot] defconfig build issues Thomas Petazzoni
2018-05-05 22:59 ` Fabio Estevam
2018-05-06 6:34 ` Peter Korsgaard
2018-05-06 13:50 ` Martin Bark
2018-05-06 15:27 ` Arnout Vandecappelle
2018-05-06 19:22 ` Peter Korsgaard [this message]
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=87muxcpp29.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.