From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Cannot build C++ internal toolchain using uclibc-ng
Date: Thu, 7 Jun 2018 10:26:46 +0200 [thread overview]
Message-ID: <20180607102646.0a6ab073@windsurf> (raw)
In-Reply-To: <CAPa8UMe7aWfRX+gRg=TawdqRaLj3CDee-gJ6Cn0w2aVdE9BkZA@mail.gmail.com>
Hello,
On Wed, 6 Jun 2018 23:24:06 +0200, Michele Bucca wrote:
> >> make clean
> >> LC_ALL=C make
> >>
> >> [1] https://pastebin.com/Z6vUVmRE
> >>
> >
> > What Linux distribution and version of this distribution are you using
> > as the host system ?
>
> My host system is Debian Jessie 8.10 x86_64 Updated just today with
> latest packages from the repos
I built your exact defconfig in a Docker container that has Debian
Jessie 8.10 installed, and it worked just fine for me. I only had an
issue way after the toolchain build, when building the kernel, because
your defconfig lacks:
BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
But other than that, it builds fine. So I suspect there is something
wrong/special in your environment. As I can't reproduce, you'll have to
investigate a bit yourself I'm afraid.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-06-07 8:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 15:41 [Buildroot] Cannot build C++ internal toolchain using uclibc-ng Michele Bucca
2018-06-06 18:49 ` Thomas Petazzoni
2018-06-06 20:29 ` Michele Bucca
2018-06-06 21:15 ` Thomas Petazzoni
2018-06-06 21:24 ` Michele Bucca
2018-06-07 8:26 ` Thomas Petazzoni [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=20180607102646.0a6ab073@windsurf \
--to=thomas.petazzoni@bootlin.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