From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] adding nodejs to buildroot
Date: Wed, 19 Feb 2014 09:27:23 +0100 [thread overview]
Message-ID: <20140219092723.112c19ab@skate> (raw)
In-Reply-To: <2DD0B9C711CDFC45A3A266C78966CE7F4531F64B@G9W0750.americas.hpqcorp.net>
Dear Jenkins, Lee (ISS Houston),
On Wed, 19 Feb 2014 00:38:16 +0000, Jenkins, Lee (ISS Houston) wrote:
> I tried to add package nodejs to an old BuildRoot : 2011.05
>
> Here's how I added the package:
> 1. I downloaded the nodejs package (Config.in, nodejs.mk, and nodejs...patch) from the latest buildroot into the buildroot/package/nodejs directory.
> 2. I added an entry for nodejs in buildroot/packages/Config.in under "Interpreter languages and scripting"
> 3. I ran "make menuconfig", selected the nodejs package (yes, it appeared in the right spot) and saved the configuration
>
> But something is out of place because the make fails:
>
> buildroot$ make nodejs
> make: *** No rule to make target `nodejs'. Stop.
You need to replace the last lines of nodejs.mk by:
$(eval $(call GENTARGETS,package,nodejs))
$(eval $(call GENTARGETS,package,nodejs,host))
However, there will most likely be a lot of other problems, as new
packages often rely on new features of the package infrastructure. So
you cannot simply take a package from a more recent version of
Buildroot, drop it in a 3 years older Buildroot and expect things to
work.
What about upgrading your Buildroot instead? By using such an old
version, you lose all the support that the community could give you,
because we are not really interested in solving issues occurring with a
3 years old Buildroot.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-19 8: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 [this message]
[not found] ` <2DD0B9C711CDFC45A3A266C78966CE7F4531FD06@G9W0750.americas.hpqcorp.net>
2014-02-19 18:27 ` Thomas Petazzoni
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=20140219092723.112c19ab@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