From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] nodejs: update to 0.4.2
Date: Wed, 16 Mar 2011 11:48:07 +0100 [thread overview]
Message-ID: <ilq4h7$35k$1@dough.gmane.org> (raw)
In-Reply-To: <4D7CD7C8.1080108@eukrea.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 13-03-11 15:42, Eric Bénard wrote:
> Hi Koen,
>
> On 12/03/2011 00:21, Koen Kooi wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 11-03-11 23:20, Eric Bénard wrote:
>>> Signed-off-by: Eric Bénard<eric@eukrea.com>
>>
>> Does this one actually build? 0.4.0 doesn't :(
>>
> strange I had 0.4.0 running on an armv5 using angstrom-2010, about 2
> weeks ago. I just tested it again and 0.4.2 builds for the same target.
I get this:
+ do_compile
+ make
Waf: Entering directory
`/OE/angstrom-2008/build/tmp-angstrom_2008_1/work/armv7a-angstrom-linux-gnueabi/nodejs-0.4.2-r0/node-v0.4.2/build'
[74/74] cxx_link: build/default/src/node_main_4.o
build/default/src/node_4.o build/default/src/node_buffer_4.o
build/default/src/node_javascript_4.o
build/default/src/node_extensions_4.o
build/default/src/node_http_parser_4.o build/default/src/node_net_4.o
build/default/src/node_io_watcher_4.o
build/default/src/node_constants_4.o build/default/src/node_cares_4.o
build/default/src/node_events_4.o build/default/src/node_file_4.o
build/default/src/node_signal_watcher_4.o
build/default/src/node_stat_watcher_4.o build/default/src/node_timer_4.o
build/default/src/node_script_4.o build/default/src/node_os_4.o
build/default/src/node_dtrace_4.o build/default/src/node_stdio_4.o
build/default/src/node_child_process_4.o
build/default/src/platform_linux_4.o build/default/src/node_crypto_4.o
build/default/deps/libeio/eio_1.o
build/default/deps/http_parser/http_parser_2.o
build/default/deps/libev/ev_1.o
build/default/deps/c-ares/ares_strcasecmp_1.o
build/default/deps/c-ares/ares_free_string_1.o
build/default/deps/c-ares/ares_options_1.o
build/default/deps/c-ares/ares_send_1.o
build/default/deps/c-ares/ares_parse_txt_reply_1.o
build/default/deps/c-ares/ares_parse_ptr_reply_1.o
build/default/deps/c-ares/ares_nowarn_1.o
build/default/deps/c-ares/ares_search_1.o
build/default/deps/c-ares/ares_gethostbyname_1.o
build/default/deps/c-ares/ares_getsock_1.o
build/default/deps/c-ares/ares__timeval_1.o
build/default/deps/c-ares/inet_ntop_1.o
build/default/deps/c-ares/ares_parse_a_reply_1.o
build/default/deps/c-ares/ares_getopt_1.o
build/default/deps/c-ares/ares__close_sockets_1.o
build/default/deps/c-ares/ares_expand_string_1.o
build/default/deps/c-ares/ares_destroy_1.o
build/default/deps/c-ares/ares_cancel_1.o
build/default/deps/c-ares/ares_parse_aaaa_reply_1.o
build/default/deps/c-ares/ares_parse_ns_reply_1.o
build/default/deps/c-ares/ares_version_1.o
build/default/deps/c-ares/ares__get_hostent_1.o
build/default/deps/c-ares/ares_writev_1.o
build/default/deps/c-ares/ares_expand_name_1.o
build/default/deps/c-ares/ares_free_hostent_1.o
build/default/deps/c-ares/ares_parse_mx_reply_1.o
build/default/deps/c-ares/ares_gethostbyaddr_1.o
build/default/deps/c-ares/ares_query_1.o
build/default/deps/c-ares/ares_data_1.o
build/default/deps/c-ares/ares_init_1.o
build/default/deps/c-ares/ares_timeout_1.o
build/default/deps/c-ares/ares_fds_1.o
build/default/deps/c-ares/inet_net_pton_1.o
build/default/deps/c-ares/ares_strerror_1.o
build/default/deps/c-ares/bitncmp_1.o
build/default/deps/c-ares/ares_getnameinfo_1.o
build/default/deps/c-ares/ares_library_init_1.o
build/default/deps/c-ares/ares_mkquery_1.o
build/default/deps/c-ares/ares_process_1.o
build/default/deps/c-ares/windows_port_1.o
build/default/deps/c-ares/ares_parse_srv_reply_1.o
build/default/deps/c-ares/ares_llist_1.o
build/default/deps/c-ares/ares__read_line_1.o
build/default/deps/c-ares/ares_strdup_1.o -> build/default/node
default/deps/libeio/eio_1.o: In function `eio__sync_file_range':
/OE/angstrom-2008/build/tmp-angstrom_2008_1/work/armv7a-angstrom-linux-gnueabi/nodejs-0.4.2-r0/node-v0.4.2/build/../deps/libeio/eio.c:918:
warning: warning: sync_file_range is not implemented and will always fail
default/src/node_stdio_4.o: In function `node::OpenPTY(v8::Arguments
const&)':
/OE/angstrom-2008/build/tmp-angstrom_2008_1/work/armv7a-angstrom-linux-gnueabi/nodejs-0.4.2-r0/node-v0.4.2/build/../src/node_stdio.cc:241:
undefined reference to `openpty'
collect2: ld returned 1 exit status
Waf: Leaving directory
`/OE/angstrom-2008/build/tmp-angstrom_2008_1/work/armv7a-angstrom-linux-gnueabi/nodejs-0.4.2-r0/node-v0.4.2/build'
koen@dominion:/OE/angstrom-2008$
For angstrom/beagleboard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNgJVnMkyGM64RGpERAtQxAJ9abFsqUaHdSPeeTaZBGs3bgkuGPQCdGzIT
9PZewAqNEe+yMXrmlWUR79A=
=0QMk
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-03-16 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 22:20 [PATCH] nodejs: update to 0.4.2 Eric Bénard
2011-03-11 23:21 ` Koen Kooi
2011-03-13 14:42 ` Eric Bénard
2011-03-13 16:44 ` Koen Kooi
2011-03-16 10:48 ` Koen Kooi [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-11 21:35 Eric Bénard
2011-03-12 0:18 ` Khem Raj
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='ilq4h7$35k$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--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