From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9001] Nodejs option not available
Date: Wed, 15 Jun 2016 12:50:50 +0000 [thread overview]
Message-ID: <bug-9001-163-H750AIMTD3@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9001-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9001
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Removing the dependency is wrong. This problem has been fixed in commit
3d2175780d70a864836c75343fd969fba1109057, which wasn't part of Buildroot
2016.05.
Basically, using Buildroot 2016.05 on a machine that has gcc 6 is not
supported. Use the latest Git if you are in such a situation.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2016-06-15 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 7:33 [Buildroot] [Bug 9001] New: Nodejs option not available bugzilla at busybox.net
2016-06-15 7:35 ` [Buildroot] [Bug 9001] " bugzilla at busybox.net
2016-06-15 12:50 ` bugzilla at busybox.net [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=bug-9001-163-H750AIMTD3@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