From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] adding nodejs to buildroot
Date: Wed, 19 Feb 2014 19:27:49 +0100 [thread overview]
Message-ID: <20140219192749.719929fa@skate> (raw)
In-Reply-To: <2DD0B9C711CDFC45A3A266C78966CE7F4531FD06@G9W0750.americas.hpqcorp.net>
Lee,
Please keep the list Cc'ed.
On Wed, 19 Feb 2014 18:12:33 +0000, Jenkins, Lee (ISS Houston) wrote:
> Thanks for the assist. With that information and a small patch to the build of host-python I was able to build node.
Cool!
> We have talked about upgrading our buildroot. Same old tradeoff convo of time/risk to upgrade vs. our looming deadline.
Yes, indeed. Unfortunately, when calculating this tradeoff, a lot of
people/companies forget that by not upgrading, they lose community
support. And this support might prove to be very useful :)
> I could post my solution to the mailing list if you think it might be useful. I realize this wouldn't be an official patch, but it might help someone operating under similar constraints.
I don't know if it would be really useful, because it's unlikely that
people having the same problem as you will find your patch amongst the
myriad of patches that are being sent to the Buildroot mailing list :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-02-19 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 0:38 [Buildroot] adding nodejs to buildroot Jenkins, Lee
2014-02-19 8:27 ` Thomas Petazzoni
[not found] ` <2DD0B9C711CDFC45A3A266C78966CE7F4531FD06@G9W0750.americas.hpqcorp.net>
2014-02-19 18:27 ` 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=20140219192749.719929fa@skate \
--to=thomas.petazzoni@free-electrons.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