From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10846] error in compiling gnutls
Date: Wed, 21 Mar 2018 19:52:38 +0000 [thread overview]
Message-ID: <bug-10846-163-nfRe6lUl69@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10846-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10846
--- Comment #6 from Peter Seiderer <ps.report@gmx.net> ---
Yes, this config.log location was the real failure reason.
The hints to the solution are:
- checking how to run the C++ preprocessor... cpp
- configure:49488: result: cpp
Your toolchain is missing C++ support (and the gnutls packages is missing
the C++ dependency), the following buildroot config change fixed the
failure for me:
$ diff -u .config.old .config
@@ -299,7 +300,7 @@
BR2_GCC_SUPPORTS_FINEGRAINEDMTUNE=y
BR2_GCC_VERSION="6.4.0"
BR2_EXTRA_GCC_CONFIG_OPTIONS=""
-# BR2_TOOLCHAIN_BUILDROOT_CXX is not set
+BR2_TOOLCHAIN_BUILDROOT_CXX=y
# BR2_TOOLCHAIN_BUILDROOT_FORTRAN is not set
# BR2_GCC_ENABLE_LTO is not set
# BR2_GCC_ENABLE_OPENMP is not set
Regards,
Peter
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-03-21 19:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 16:50 [Buildroot] [Bug 10846] New: error in compiling gnutls bugzilla at busybox.net
2018-03-06 21:19 ` [Buildroot] [Bug 10846] " bugzilla at busybox.net
2018-03-17 17:05 ` bugzilla at busybox.net
2018-03-17 17:07 ` bugzilla at busybox.net
2018-03-17 17:09 ` bugzilla at busybox.net
2018-03-17 17:11 ` bugzilla at busybox.net
2018-03-21 19:52 ` bugzilla at busybox.net [this message]
2018-03-23 14:55 ` bugzilla at busybox.net
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=bug-10846-163-nfRe6lUl69@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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