Skip to content

Instantly share code, notes, and snippets.

@lamnk
Created October 4, 2010 04:44
Show Gist options
  • Save lamnk/609252 to your computer and use it in GitHub Desktop.
Save lamnk/609252 to your computer and use it in GitHub Desktop.
default/deps/libeio/eio_1.o: In function `eio__sync_file_range':
/home/lamnk/builds/node/build/../deps/libeio/eio.c:874: undefined reference to `sync_file_range'
/home/lamnk/builds/node/build/../deps/libeio/eio.c:874: undefined reference to `sync_file_range'
default/deps/libev/ev_1.o: In function `ev_signal_stop':
/home/lamnk/builds/node/build/../deps/libev/ev.c:2801: undefined reference to `signalfd'
default/deps/libev/ev_1.o: In function `evpipe_init':
/home/lamnk/builds/node/build/../deps/libev/ev.c:1197: undefined reference to `eventfd'
/home/lamnk/builds/node/build/../deps/libev/ev.c:1199: undefined reference to `eventfd'
default/deps/libev/ev_1.o: In function `ev_signal_start':
/home/lamnk/builds/node/build/../deps/libev/ev.c:2740: undefined reference to `signalfd'
/home/lamnk/builds/node/build/../deps/libev/ev.c:2717: undefined reference to `signalfd'
/home/lamnk/builds/node/build/../deps/libev/ev.c:2719: undefined reference to `signalfd'
collect2: ld returned 1 exit status
Waf: Leaving directory `/home/lamnk/builds/node/build'
Build failed: -> task failed (err #1):
{task: cxx_link node_main_4.o,node_4.o,node_buffer_4.o,node_extensions_4.o,node_http_parser_4.o,node_net_4.o,node_io_watcher_4.o,node_child_process_4.o,node_constants_4.o,node_cares_4.o,node_events_4.o,node_file_4.o,node_signal_watcher_4.o,node_stat_watcher_4.o,node_stdio_4.o,node_timer_4.o,node_script_4.o,platform_linux_4.o,node_crypto_4.o,eio_1.o,http_parser_2.o,ev_1.o,ares_strcasecmp_1.o,ares_free_string_1.o,ares_options_1.o,ares_send_1.o,ares_parse_txt_reply_1.o,ares_parse_ptr_reply_1.o,ares_nowarn_1.o,ares_search_1.o,ares_gethostbyname_1.o,ares_getsock_1.o,ares__timeval_1.o,inet_ntop_1.o,ares_parse_a_reply_1.o,ares_getopt_1.o,ares__close_sockets_1.o,ares_expand_string_1.o,ares_destroy_1.o,ares_cancel_1.o,ares_parse_aaaa_reply_1.o,ares_parse_ns_reply_1.o,ares_version_1.o,ares__get_hostent_1.o,ares_writev_1.o,ares_expand_name_1.o,ares_free_hostent_1.o,ares_parse_mx_reply_1.o,ares_gethostbyaddr_1.o,ares_query_1.o,ares_data_1.o,ares_init_1.o,ares_timeout_1.o,ares_fds_1.o,inet_net_pton_1.o,ares_strerror_1.o,bitncmp_1.o,ares_getnameinfo_1.o,ares_library_init_1.o,ares_mkquery_1.o,ares_process_1.o,windows_port_1.o,ares_parse_srv_reply_1.o,ares_llist_1.o,ares__read_line_1.o,ares_strdup_1.o -> node}
make: *** [all] Error 1
lamnk@lamnk:~/builds/node% g++ -v
Using built-in specs.
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-libgcj-multifile --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --enable-plugin --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre --with-cpu=generic --host=x86_64-redhat-linux
Thread model: posix
gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)
lamnk@lamnk:~/builds/node% uname -a
Linux lamnk 2.6.18-194.17.1.el5 #1 SMP Wed Sep 29 12:50:31 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
@lamnk
Copy link
Author

lamnk commented Oct 15, 2010

Yep, see at the end of this issue:
http://github.com/ry/node/issues#issue/170

Latest commits failed. I've compiled node successfully against commit d59512f6f406ceae4940

@rfb
Copy link

rfb commented Oct 16, 2010

Ah, cool, I did the same. Thanks for getting back to me.

@robhawkes
Copy link

Unfortunately the old commits contain issues that cause me issues while using Socket.IO. How can we go about getting the latest builds to work? I'm on CentOS 5.

@lamnk
Copy link
Author

lamnk commented Oct 18, 2010

I fetched latest upstream changes and nodejs compiled cleanly now
# node -v
v0.3.0-pre

@robhawkes
Copy link

Thanks lamnk. How do I go about getting v0.3.0-pre? I can't see to find it anywhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment