Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v4] nodejs: updated recipe to v0.2.6
Date: Wed, 09 Feb 2011 13:42:28 -0700	[thread overview]
Message-ID: <4D52FC34.9020401@mentor.com> (raw)
In-Reply-To: <iius8b$ke3$1@dough.gmane.org>

On 02/09/2011 01:08 PM, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 09-02-11 20:44, Tom Rini wrote:
>> On 02/08/2011 10:58 AM, AJ ONeal wrote:
>>> * added version number to patches
>>> * libev-cross-cc_0.2.6.patch - turns off execution so that
>>> cross-compile succeeds
>>> * node-cross-cc_0.2.6.patch - enables cross-compiling of v8 for x86,
>>> x86_64, arm, and mips
>>
>> I didn't touch it in patchwork but (and I see these aren't all new issues):
>>
>>> diff --git a/recipes/nodejs/nodejs_0.2.6.bb
>>> b/recipes/nodejs/nodejs_0.2.6.bb
>>> new file mode 100644
>>> index 0000000..560adc6
>>> --- /dev/null
>>> +++ b/recipes/nodejs/nodejs_0.2.6.bb
>>> @@ -0,0 +1,32 @@
>>> +DESCRIPTION = "nodeJS Evented I/O for V8 JavaScript"
>>> +HOMEPAGE = "http://nodejs.org"
>>> +LICENSE = "MIT"
>>> +
>>> +DEPENDS = "openssl"
>>> +
>>> +SRC_URI = " \
>>> +  http://nodejs.org/dist/node-v${PV}.tar.gz \
>>> +  file://libev-cross-cc-v${PV}.patch \
>>> +  file://node-cross-cc-v${PV}.patch \
>>> +"
>>> +SRC_URI[md5sum] = "b1c50ceb43bee1b221be210b7bc7a216"
>>> +SRC_URI[sha256sum] =
>>> "e97fe9c81ff4b569ae9a0d46e64a0572a1f171293573a5b5290bcc3996a19701"
>>> +
>>> +S = "${WORKDIR}/node-v${PV}"
>>> +
>>> +# v8 errors out if you have set CCACHE
>>> +CCACHE = ""
>>> +
>>> +do_configure () {
>>> +  ./configure --prefix=${prefix} --without-snapshot
>>> +}
>>
>> Why isn't this just EXTRA_OECONF = "--without-snapshot" and using the
>> default do_configure, compile and install?
>
> It's one of those python abominations that try to look like autotools :(
> And as usual, it has even more bugs than autotools when you try to
> crosscompile

Retch.  So, unless someone pops up within the next 24h and says why they 
did something in patchwork or otherwise objects, I'll push this.  Thanks!

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2011-02-09 20:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08 17:58 [PATCH v4] nodejs: updated recipe to v0.2.6 AJ ONeal
2011-02-09 19:44 ` Tom Rini
2011-02-09 20:08   ` Koen Kooi
2011-02-09 20:42     ` Tom Rini [this message]
2011-02-10  1:37       ` Khem Raj
2011-02-10 19:04         ` AJ ONeal

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=4D52FC34.9020401@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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