Add nodejs to LibraryBox

[kevinold]

Hi,

I would like to add nodejs to my LibraryBox and have found this: https://github.com/akwrt/openwrt-nodejs but I am unclear on how I can incorporate it with the current LibraryBox builds.

Would someone be able to help?

[griffey]

I tried an early build of Node.js for OpenWRT, and it was....unsuitable.
Really buggy, slow, caused all sorts of performance problems. We can look
at this release to see if it's any better...

Jason

On Fri, Sep 18, 2015 at 9:59 PM Kevin Old notifications@github.com wrote:

Hi,

I would like to add nodejs to my LibraryBox and have found this:
https://github.com/akwrt/openwrt-nodejs but I am unclear on how I can
incorporate it with the current LibraryBox builds.

Would someone be able to help?

—
Reply to this email directly or view it on GitHub
#26.

[kevinold]

Awesome! This script uses Node 0.10.25, but v4.0.0 was just released so it might make sense to try that version.

I'm also interested in compiling Elixir with OpenWRT, but need a bit of guidance in understand what prerequisites are needed when compiling. I filed this issue on OpenWRT, but would ulimately love to have this on LibraryBox openwrt/packages#1786

[kevinold]

I tested building nodejs into OpenWRT with the script I referenced, and I'm running into the following:

I think it is because I'm using OpenWRT 15 instead of an earlier version and that it is not compatible with gcc 4.6.

I found this that seems to solve it, but references gcc 4.9: https://dev.openwrt.org/ticket/18182

s" BUILDTYPE=Release  ;
make[4]: Entering directory `/home/vagrant/openwrt/build_dir/target-mips_34kc_musl-1.1.11/node-v0.10.25'
make -C out BUILDTYPE=Release V=s
make[5]: Entering directory `/home/vagrant/openwrt/build_dir/target-mips_34kc_musl-1.1.11/node-v0.10.25/out'
  mips-openwrt-linux-musl-gcc '-DL_ENDIAN' '-DPURIFY' '-D_REENTRANT' '-DOPENSSL_NO_HEARTBEATS' '-DOPENSSL_NO_ASM' '-DENGINESDIR="/dev/null"' '-DOPENSSLDIR="/etc/ssl"' '-DTERMIOS' -I../deps/openssl -I../deps/openssl/openssl -I../deps/openssl/openssl/crypto -I../deps/openssl/openssl/crypto/asn1 -I../deps/openssl/openssl/crypto/evp -I../deps/openssl/openssl/crypto/md2 -I../deps/openssl/openssl/crypto/modes -I../deps/openssl/openssl/crypto/store -I../deps/openssl/openssl/include  -Wall -Wextra -Wno-unused-parameter -pthread -Wno-missing-field-initializers -Wno-old-style-declaration -O2 -fno-strict-aliasing -fno-tree-vrp -fno-omit-frame-pointer  -MMD -MF /home/vagrant/openwrt/build_dir/target-mips_34kc_musl-1.1.11/node-v0.10.25/out/Release/.deps//home/vagrant/openwrt/build_dir/target-mips_34kc_musl-1.1.11/node-v0.10.25/out/Release/obj.target/openssl/deps/openssl/openssl/crypto/ui/ui_openssl.o.d.raw -Os -pipe -mno-branch-likely -mips32r2 -mtune=34kc -fno-caller-saves -fhonour-copts -Wno-error=unused-but-set-variable -msoft-float -mips16 -minterlink-mips16 -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro  -I/home/vagrant/openwrt/staging_dir/target-mips_34kc_musl-1.1.11/usr/include -I/home/vagrant/openwrt/staging_dir/target-mips_34kc_musl-1.1.11/include -I/home/vagrant/openwrt/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_musl-1.1.11/usr/include -I/home/vagrant/openwrt/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_musl-1.1.11/include/fortify -I/home/vagrant/openwrt/staging_dir/toolchain-mips_34kc_gcc-4.8-linaro_musl-1.1.11/include  -c -o /home/vagrant/openwrt/build_dir/target-mips_34kc_musl-1.1.11/node-v0.10.25/out/Release/obj.target/openssl/deps/openssl/openssl/crypto/ui/ui_openssl.o ../deps/openssl/openssl/crypto/ui/ui_openssl.c
../deps/openssl/openssl/crypto/ui/ui_openssl.c:232:21: fatal error: termio.h: No such file or directory
 # include <termio.h>
                     ^
compilation terminated.
make[5]: *** [/home/vagrant/openwrt/build_dir/target-mips_34kc_musl-1.1.11/node-v0.10.25/out/Release/obj.target/openssl/deps/openssl/openssl/crypto/ui/ui_openssl.o] Error 1
make[5]: Leaving directory `/home/vagrant/openwrt/build_dir/target-mips_34kc_musl-1.1.11/node-v0.10.25/out'
make[4]: *** [node] Error 2
make[4]: Leaving directory `/home/vagrant/openwrt/build_dir/target-mips_34kc_musl-1.1.11/node-v0.10.25'
make[3]: *** [/home/vagrant/openwrt/build_dir/target-mips_34kc_musl-1.1.11/node-v0.10.25/.built] Error 2
make[3]: Leaving directory `/home/vagrant/openwrt/feeds/nodejs/nodejs'
make[2]: *** [package/feeds/nodejs/nodejs/compile] Error 2
make[2]: Leaving directory `/home/vagrant/openwrt'
make[1]: *** [/home/vagrant/openwrt/staging_dir/target-mips_34kc_musl-1.1.11/stamp/.package_compile] Error 2
make[1]: Leaving directory `/home/vagrant/openwrt'
make: *** [world] Error 2

vagrant@precise32:~/openwrt$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/4.6/lto-wrapper
Target: i686-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.6.3-1ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.6 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin --enable-objc-gc --enable-targets=all --disable-werror --with-arch-32=i686 --with-tune=generic --enable-checking=release --build=i686-linux-gnu --host=i686-linux-gnu --target=i686-linux-gnu
Thread model: posix
gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)

[kevinold]

It's also worth noting that they've started compiling releases for arm with each release: https://nodejs.org/download/release/v4.1.0/node-v4.1.0-linux-armv7l.tar.gz

Would I be able to just copy these builds over the TP Link MR3040?

[jfathman]

My Node.js on ARM experience is limited to Raspberry Pi and BeagleBone where others have figured out the porting issues (and we thank them). As a suggestion, you might look over the Omega Onion project which is rather prominently introducing Node.js on a minimal OpenWRT platform.

https://onion.io/omega

https://github.com/OnionIoT/OpenWRT-Packages/tree/master/iojs

You might find some source or discussion that could get you going. I think the Tessel 2 project may also be Node.js on OpenWRT.

[griffey]

We'll look into it asap, gang. I, too, would like node.js on the platform, for server-side epub rendering. :-) Let me dig in this week and see what I can find out.

[kevinold]

Awesome! I've attempted to compile the iojs linked from @jfathman but am running into compile errors. I'll keep trying but probably with a v3 or v4.

I've also run across nodejs/node#2948 which is relevant and could help us.

[kevinold]

Extremely naive question, but now that nodejs provides builds for arm, can't we use its Makefile directly

[kevinold]

Accidentally closed sorry, reopened

[kevinold]

https://github.com/nodejs/node/blob/master/Makefile Search for "arm" and you'll see the ARCH is modified accordingly. Combine that with lots of flags throughout the code for ARM architecture https://github.com/nodejs/node/search?utf8=✓&q=arm

[MaStr]

maybe to clear things up a bit:
ARM(Raspberry) != MIPS (Alot mini routers)

So, binaries aren't replacable/re-usable.

The gcc of your system is only a kickstart gcc. The real gcc used in the buildchain is compiled by the OpenWrt toolchain itself.

You need to add this package via a package-feed to your build environment and mark it as a "module" using "make menuconfig". After that compile it with "make -j3".

[kevinold]

Thanks for the clarification @MaStr. As I said, it was an extremely naive question. :)

I had already started to compile iojs v2.3.0 using the reference to the Onion scripts above, but ran into a compile error.

I've just kicked off a build of this https://github.com/kevinold/openwrt-nodejs which updates the script node 4.1.0. I will report back with progress.

[kevinold]

I've been trying to get the compile to run all day but it seems the git server that hosts the mtd-utils package is returning an error:

echo "Checking out files from the git repository..."; mkdir -p /home/vagrant/openwrt-dev-environment/openwrt/tmp/dl && cd /home/vagrant/openwrt-dev-environment/openwrt/tmp/dl && rm -rf mtd-utils-1.4.5 && [ \! -d mtd-utils-1.4.5 ] && git clone git://git.infradead.org/mtd-utils.git mtd-utils-1.4.5 --recursive && (cd mtd-utils-1.4.5 && git checkout 5319b84974fcb71504aed2d1b8285e9c0a4a4bb8) && echo "Packing checkout..." && rm -rf mtd-utils-1.4.5/.git &&   /bin/tar cfz /home/vagrant/openwrt-dev-environment/openwrt/tmp/dl/mtd-utils-1.4.5.tar.gz mtd-utils-1.4.5 && mv /home/vagrant/openwrt-dev-environment/openwrt/tmp/dl/mtd-utils-1.4.5.tar.gz /home/vagrant/openwrt-dev-environment/openwrt/dl/ && rm -rf mtd-utils-1.4.5;
Checking out files from the git repository...
Cloning into 'mtd-utils-1.4.5'...
fatal: The remote end hung up unexpectedly
make[3]: *** [/home/vagrant/openwrt-dev-environment/openwrt/dl/mtd-utils-1.4.5.tar.gz] Error 128
make[3]: Leaving directory `/home/vagrant/openwrt-dev-environment/openwrt/tools/mtd-utils'
make[2]: *** [tools/mtd-utils/compile] Error 2
make[2]: Leaving directory `/home/vagrant/openwrt-dev-environment/openwrt'
make[1]: *** [/home/vagrant/openwrt-dev-environment/openwrt/staging_dir/target-mips_r2_uClibc-0.9.33.2/stamp/.tools_install_nnnnn] Error 2
make[1]: Leaving directory `/home/vagrant/openwrt-dev-environment/openwrt'
make: *** [world] Error 2

I've tried every hour or two and it's still throwing it. Hoping the git server stops "hanging up" at some point. The web version is accessible.