However, I don't see how it could work. There is a #ifdef that does not include s390x, and the else case is an #error

[  249s] ../deps/v8z/src/gdb-jit.cc:682:2: error: #error Unsupported target architecture.
[  249s]  #error Unsupported target architecture.

Full log of the build:

  242s]   g++ '-DENABLE_DEBUGGER_SUPPORT' '-DENABLE_EXTRA_CHECKS' '-DENABLE_GDB_JIT_INTERFACE' '-DV8_TARGET_ARCH_S390' '-DV8_TARGET_ARCH_S390X' -I../deps/v8z/src  -DOPENSSL_LOAD_CONF -Wall -Wextra -Wno-unused-parameter -pthread -fno-strict-aliasing -O2 -fno-strict-aliasing -fno-tree-vrp -fno-omit-frame-pointer -fno-rtti -fno-exceptions -MMD -MF /home/abuild/rpmbuild/BUILD/node-0.10.33-release-ppc/out/Release/.deps//home/abuild/rpmbuild/BUILD/node-0.10.33-release-ppc/out/Release/obj.target/v8_base/deps/v8z/src/full-codegen.o.d.raw -fmessage-length=0 -grecord-gcc-switches -fstack-protector -O2 -Wall -D_FORTIFY_SOURCE=2 -funwind-tables -fasynchronous-unwind-tables -c -o /home/abuild/rpmbuild/BUILD/node-0.10.33-release-ppc/out/Release/obj.target/v8_base/deps/v8z/src/full-codegen.o ../deps/v8z/src/full-codegen.cc
[  247s]   g++ '-DENABLE_DEBUGGER_SUPPORT' '-DENABLE_EXTRA_CHECKS' '-DENABLE_GDB_JIT_INTERFACE' '-DV8_TARGET_ARCH_S390' '-DV8_TARGET_ARCH_S390X' -I../deps/v8z/src  -DOPENSSL_LOAD_CONF -Wall -Wextra -Wno-unused-parameter -pthread -fno-strict-aliasing -O2 -fno-strict-aliasing -fno-tree-vrp -fno-omit-frame-pointer -fno-rtti -fno-exceptions -MMD -MF /home/abuild/rpmbuild/BUILD/node-0.10.33-release-ppc/out/Release/.deps//home/abuild/rpmbuild/BUILD/node-0.10.33-release-ppc/out/Release/obj.target/v8_base/deps/v8z/src/func-name-inferrer.o.d.raw -fmessage-length=0 -grecord-gcc-switches -fstack-protector -O2 -Wall -D_FORTIFY_SOURCE=2 -funwind-tables -fasynchronous-unwind-tables -c -o /home/abuild/rpmbuild/BUILD/node-0.10.33-release-ppc/out/Release/obj.target/v8_base/deps/v8z/src/func-name-inferrer.o ../deps/v8z/src/func-name-inferrer.cc
[  249s]   g++ '-DENABLE_DEBUGGER_SUPPORT' '-DENABLE_EXTRA_CHECKS' '-DENABLE_GDB_JIT_INTERFACE' '-DV8_TARGET_ARCH_S390' '-DV8_TARGET_ARCH_S390X' -I../deps/v8z/src  -DOPENSSL_LOAD_CONF -Wall -Wextra -Wno-unused-parameter -pthread -fno-strict-aliasing -O2 -fno-strict-aliasing -fno-tree-vrp -fno-omit-frame-pointer -fno-rtti -fno-exceptions -MMD -MF /home/abuild/rpmbuild/BUILD/node-0.10.33-release-ppc/out/Release/.deps//home/abuild/rpmbuild/BUILD/node-0.10.33-release-ppc/out/Release/obj.target/v8_base/deps/v8z/src/gdb-jit.o.d.raw -fmessage-length=0 -grecord-gcc-switches -fstack-protector -O2 -Wall -D_FORTIFY_SOURCE=2 -funwind-tables -fasynchronous-unwind-tables -c -o /home/abuild/rpmbuild/BUILD/node-0.10.33-release-ppc/out/Release/obj.target/v8_base/deps/v8z/src/gdb-jit.o ../deps/v8z/src/gdb-jit.cc
[  249s] ../deps/v8z/src/gdb-jit.cc:682:2: error: #error Unsupported target architecture.
[  249s]  #error Unsupported target architecture.
[  249s]   ^
[  249s] ../deps/v8z/src/gdb-jit.cc:698:2: error: #error Unsupported target architecture.
[  249s]  #error Unsupported target architecture.
[  249s]   ^
[  249s] ../deps/v8z/src/gdb-jit.cc:1118:2: error: #error Unsupported target architecture.
[  249s]  #error Unsupported target architecture.
[  249s]   ^
[  250s] ../deps/v8z/src/gdb-jit.cc: In member function 'void v8::internal::ELF::WriteHeader(v8::internal::Writer*)':
[  250s] ../deps/v8z/src/gdb-jit.cc:684:27: error: 'ident' was not declared in this scope
[  250s]      memcpy(header->ident, ident, 16);
[  250s]                            ^
[  250s] ../deps/v8z/src/gdb-jit.cc: At global scope:
[  250s] ../deps/v8z/src/gdb-jit.cc:835:27: error: 'SerializedLayout' was not declared in this scope
[  250s]    void Write(Writer::Slot<SerializedLayout> s, StringTable* t) {
[  250s]                            ^
[  250s] ../deps/v8z/src/gdb-jit.cc:835:43: error: template argument 1 is invalid
[  250s]    void Write(Writer::Slot<SerializedLayout> s, StringTable* t) {
[  250s]                                            ^
[  250s] ../deps/v8z/src/gdb-jit.cc: In member function 'void v8::internal::ELFSymbol::Write(int, v8::internal::StringTable*)':
[  250s] ../deps/v8z/src/gdb-jit.cc:837:6: error: base operand of '->' is not a pointer
[  250s]      s->name = t->Add(name);
[  250s]       ^
[  250s] ../deps/v8z/src/gdb-jit.cc:838:6: error: base operand of '->' is not a pointer
[  250s]      s->value = value;
[  250s]       ^
[  250s] ../deps/v8z/src/gdb-jit.cc:839:6: error: base operand of '->' is not a pointer
[  250s]      s->size = size;
[  250s]       ^
[  250s] ../deps/v8z/src/gdb-jit.cc:840:6: error: base operand of '->' is not a pointer
[  250s]      s->info = info;
[  250s]       ^
[  250s] ../deps/v8z/src/gdb-jit.cc:841:6: error: base operand of '->' is not a pointer
[  250s]      s->other = other;
[  250s]       ^
[  250s] ../deps/v8z/src/gdb-jit.cc:842:6: error: base operand of '->' is not a pointer
[  250s]      s->section = section;
[  250s]       ^
[  250s] ../deps/v8z/src/gdb-jit.cc: At global scope:
[  250s] ../deps/v8z/src/gdb-jit.cc:907:38: error: 'SerializedLayout' is not a member of 'v8::internal::ELFSymbol'
[  250s]                          Writer::Slot<ELFSymbol::SerializedLayout> dst,
[  250s]                                       ^
[  250s] ../deps/v8z/src/gdb-jit.cc:907:38: error: 'SerializedLayout' is not a member of 'v8::internal::ELFSymbol'
[  250s] ../deps/v8z/src/gdb-jit.cc:907:65: error: template argument 1 is invalid
[  250s]                          Writer::Slot<ELFSymbol::SerializedLayout> dst,
[  250s]                                                                  ^
[  250s] ../deps/v8z/src/gdb-jit.cc: In member function 'virtual void v8::internal::ELFSymbolTable::WriteBody(v8::internal::Writer::Slot<v8::internal::ELFSectionHeader>, v8::internal::Writer*)':
[  250s] ../deps/v8z/src/gdb-jit.cc:868:18: error: 'SerializedLayout' is not a member of 'v8::internal::ELFSymbol'
[  250s]      Writer::Slot<ELFSymbol::SerializedLayout> symbols =
[  250s]                   ^
[  250s] ../deps/v8z/src/gdb-jit.cc:868:18: error: 'SerializedLayout' is not a member of 'v8::internal::ELFSymbol'
[  250s] ../deps/v8z/src/gdb-jit.cc:868:45: error: template argument 1 is invalid
[  250s]      Writer::Slot<ELFSymbol::SerializedLayout> symbols =
[  250s]                                              ^
[  250s] ../deps/v8z/src/gdb-jit.cc:868:55: error: invalid type in declaration before '=' token
[  250s]      Writer::Slot<ELFSymbol::SerializedLayout> symbols =
[  250s]                                                        ^
[  250s] ../deps/v8z/src/gdb-jit.cc:869:28: error: 'SerializedLayout' is not a member of 'v8::internal::ELFSymbol'
[  250s]          w->CreateSlotsHere<ELFSymbol::SerializedLayout>(total_symbols);
[  250s]                             ^
[  250s] ../deps/v8z/src/gdb-jit.cc:869:28: error: 'SerializedLayout' is not a member of 'v8::internal::ELFSymbol'
[  250s] ../deps/v8z/src/gdb-jit.cc:869:70: error: no matching function for call to 'v8::internal::Writer::CreateSlotsHere(int&)'
[  250s]          w->CreateSlotsHere<ELFSymbol::SerializedLayout>(total_symbols);
[  250s]                                                                       ^
[  250s] ../deps/v8z/src/gdb-jit.cc:869:70: note: candidate is:
[  250s] ../deps/v8z/src/gdb-jit.cc:117:11: note: template<class T> v8::internal::Writer::Slot<T> v8::internal::Writer::CreateSlotsHere(uint32_t)
[  250s]    Slot<T> CreateSlotsHere(uint32_t count) {
[  250s]            ^
[  250s] ../deps/v8z/src/gdb-jit.cc:117:11: note:   template argument deduction/substitution failed:
[  250s] ../deps/v8z/src/gdb-jit.cc:869:70: error: template argument 1 is invalid
[  250s]          w->CreateSlotsHere<ELFSymbol::SerializedLayout>(total_symbols);
[  250s]                                                                       ^
[  250s] ../deps/v8z/src/gdb-jit.cc:877:13: error: request for member 'at' in 'symbols', which is of non-class type 'int'
[  250s]      symbols.at(0).set(ELFSymbol::SerializedLayout(0,
[  250s]              ^
[  250s] ../deps/v8z/src/gdb-jit.cc:877:23: error: 'SerializedLayout' is not a member of 'v8::internal::ELFSymbol'
[  250s]      symbols.at(0).set(ELFSymbol::SerializedLayout(0,
[  250s]                        ^
[  250s] ../deps/v8z/src/gdb-jit.cc:883:40: error: request for member 'at' in 'symbols', which is of non-class type 'int'
[  250s]      WriteSymbolsList(&locals_, symbols.at(1), strtab);
[  250s]                                         ^
[  250s] ../deps/v8z/src/gdb-jit.cc:884:41: error: request for member 'at' in 'symbols', which is of non-class type 'int'
[  250s]      WriteSymbolsList(&globals_, symbols.at(locals_.length() + 1), strtab);
[  250s]                                          ^
[  250s] ../deps/v8z/src/gdb-jit.cc: In member function 'virtual void v8::internal::ELFSymbolTable::PopulateHeader(v8::internal::Writer::Slot<v8::internal::ELFSectionHeader>)':
[  250s] ../deps/v8z/src/gdb-jit.cc:902:33: error: 'SerializedLayout' is not a member of 'v8::internal::ELFSymbol'
[  250s]      header->entry_size = sizeof(ELFSymbol::SerializedLayout);
[  250s]                                  ^
[  250s] ../deps/v8z/src/gdb-jit.cc: In member function 'void v8::internal::ELFSymbolTable::WriteSymbolsList(const v8::internal::ZoneList<v8::internal::ELFSymbol>*, int, v8::internal::StringTable*)':
[  250s] ../deps/v8z/src/gdb-jit.cc:912:28: error: request for member 'at' in 'dst', which is of non-class type 'int'
[  250s]        src->at(i).Write(dst.at(i), strtab);
[  250s]                             ^
[  251s] deps/v8z/tools/gyp/v8_base.target.mk:223: recipe for target '/home/abuild/rpmbuild/BUILD/node-0.10.33-release-ppc/out/Release/obj.target/v8_base/deps/v8z/src/gdb-jit.o' failed
[  251s] make[1]: *** [/home/abuild/rpmbuild/BUILD/node-0.10.33-release-ppc/out/Release/obj.target/v8_base/deps/v8z/src/gdb-jit.o] Error 1
[  251s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/node-0.10.33-release-ppc/out'
[  251s] Makefile:38: recipe for target 'node' failed
[  251s] make: *** [node] Error 2
[  251s] error: Bad exit status from /var/tmp/rpm-tmp.wo1TdS (%build)
[  251s] 

Failure stack:

assert.js:98
  throw new assert.AssertionError({
        ^
AssertionError: false == true
    at null._onTimeout (/home/tunniclm/Projects/node.aix/test/simple/test-net-settimeout.js:54:12)
    at Timer.listOnTimeout (timers.js:132:15)

-bash-4.1$ ./node --max-stack-size=1000
./node: bad option: --max-stack-size=1000
-bash-4.1$ ./node --help
Usage: node [options] [ -e script | script.js ] [arguments]
node debug script.js [arguments]

Options:
-v, --version print node's version
-e, --eval script evaluate script
-p, --print evaluate script and print result
-i, --interactive always enter the REPL even if stdin
does not appear to be a terminal
--no-deprecation silence deprecation warnings
--trace-deprecation show stack traces on deprecations
--v8-options print v8 command line options
--max-stack-size=val set max v8 stack size (bytes)

Environment variables:
NODE_PATH ':'-separated list of directories
prefixed to the module search path.
NODE_MODULE_CONTEXTS Set to 1 to load modules in their own
global contexts.
NODE_DISABLE_COLORS Set to 1 to disable colors in the REPL

Documentation can be found at http://nodejs.org/
-bash-4.1$

:/u/slbld>npm install -g loopback-connector-soap
npm WARN engine [email protected]: wanted: {"node":">= 4"} (current: {"node":"0.12.17","npm":"2.15.1"})
npm WARN deprecated [email protected]: use uuid module instead
npm WARN engine [email protected]: wanted: {"node":">=4.0"} (current: {"node":"0.12.17","npm":"2.15.1"})
\

[email protected] install /u/slbld/node/lib/node_modules/loopback-connector-soap/node_modules/strong-soap/node_modules/ursa
node-gyp rebuild

make: Entering directory '/u/slbld/node/lib/node_modules/loopback-connector-soap/node_modules/strong-soap/node_modules/ursa/build'
CXX(target) Release/obj.target/ursaNative/src/ursaNative.o
make: execvp: g++: EDC5111I Permission denied.
ursaNative.target.mk:97: recipe for target 'Release/obj.target/ursaNative/src/ursaNative.o' failed
make: *** [Release/obj.target/ursaNative/src/ursaNative.o] Error 127
make: Leaving directory '/u/slbld/node/lib/node_modules/loopback-connector-soap/node_modules/strong-soap/node_modules/ursa/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/u/slbld/node/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack at ChildProcess.emit (events.js:110:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:1078:12)
gyp ERR! System Öâaóùð òôKðð
gyp ERR! command "node" "/u/slbld/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /u/slbld/node/lib/node_modules/loopback-connector-soap/node_modules/strong-soap/node_modules/ursa
gyp ERR! node -v v0.12.17
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok
npm WARN optional dep failed, continuing [email protected]
[email protected] /u/slbld/node/lib/node_modules/loopback-connector-soap
├── [email protected] ([email protected])
├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
└── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
:/u/slbld>

environment: [email protected]
:/u/slbld>npm -v
2.15.1
n:/u/slbld>node -v
v0.12.17

Hi,

I'm trying to build 0.11.13.ppc on an AIX6.1 box, but get link errors.

The machine & compiler spec:

bash-4.3$ uname -a
AIX hhdtrlaix08 1 6 00F905954C00

bash-4.3$ oslevel -s
6100-07-09-1341

bash-4.3$ make -v
GNU Make 3.82
Built for powerpc-ibm-aix5.3.0.0

bash-4.3$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/opt/freeware/libexec/gcc/powerpc-ibm-aix6.1.0.0/4.6.1/lto-wrapper
Target: powerpc-ibm-aix6.1.0.0
Configured with: ../gcc-4.6.1/configure --with-as=/usr/bin/as --with-ld=/usr/bin/ld --enable-languages=c,c++,fortran --prefix=/opt/freeware --mandir=/opt/freeware/man --infodir=/opt/freeware/info --enable-threads --enable-version-specific-runtime-libs --disable-nls --enable-decimal-float=dpd --host=powerpc-ibm-aix6.1.0.0
Thread model: aix
gcc version 4.6.1 (GCC)

bash-4.3$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/opt/freeware/libexec/gcc/powerpc-ibm-aix6.1.0.0/4.6.1/lto-wrapper
Target: powerpc-ibm-aix6.1.0.0
Configured with: ../gcc-4.6.1/configure --with-as=/usr/bin/as --with-ld=/usr/bin/ld --enable-languages=c,c++,fortran --prefix=/opt/freeware --mandir=/opt/freeware/man --infodir=/opt/freeware/info --enable-threads --enable-version-specific-runtime-libs --disable-nls --enable-decimal-float=dpd --host=powerpc-ibm-aix6.1.0.0
Thread model: aix
gcc version 4.6.1 (GCC)

I ran ./configure then make, and the build seemed to get most of the way through without any issues, but then fails with the following error:

./gyp-flock-tool flock /home/ihayden/aix/node0.11.13/node-0.11.13-release-ppc/out/Release/linker.lock /opt/freeware/bin/g++ -Wl,-bmaxdata:0x60000000/dsa -Wl,-bmaxdata:0x60000000/dsa -o /home/ihayden/aix/node0.11.13/node-0.11.13-release-ppc/out/Release/mksnapshot.ppc /home/ihayden/aix/node0.11.13/node-0.11.13-release-ppc/out/Release/obj.target/mksnapshot.ppc/deps/v8ppc/src/mksnapshot.o /home/ihayden/aix/node0.11.13/node-0.11.13-release-ppc/out/Release/obj.target/deps/v8ppc/tools/gyp/libv8_base.ppc.a /home/ihayden/aix/node0.11.13/node-0.11.13-release-ppc/out/Release/obj.target/deps/v8ppc/tools/gyp/libv8_nosnapshot.ppc.a
ld: 0711-317 ERROR: Undefined symbol: .pthread_getspecific
ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_lock
ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_unlock
ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_init
ld: 0711-317 ERROR: Undefined symbol: .pthread_setspecific
ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_destroy
ld: 0711-317 ERROR: Undefined symbol: .pthread_join
ld: 0711-317 ERROR: Undefined symbol: .pthread_attr_init
ld: 0711-317 ERROR: Undefined symbol: .pthread_attr_setstacksize
ld: 0711-317 ERROR: Undefined symbol: .pthread_create
ld: 0711-317 ERROR: Undefined symbol: .pthread_attr_destroy
ld: 0711-317 ERROR: Undefined symbol: .pthread_self
ld: 0711-317 ERROR: Undefined symbol: .pthread_kill
ld: 0711-317 ERROR: Undefined symbol: .pthread_key_create
ld: 0711-317 ERROR: Undefined symbol: .pthread_mutexattr_init
ld: 0711-317 ERROR: Undefined symbol: .pthread_mutexattr_settype
ld: 0711-317 ERROR: Undefined symbol: .pthread_mutexattr_destroy
ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information.
collect2: ld returned 8 exit status

I understand this is supposed to build out-of-the-box, however the missing symbols appear to come from libpthreads.a so I'm not sure how anyone can get it to build if this is missing from the link.
Is there something out-of-date on our box, or some other configuration or dependency that we've missed?

Hi Andrew,
it's not an issue, but more of a question. I have this My Book Live Duo (Software Raid) running a Debian Linux. I would like to know, what steps I would need to do, to install / compile node.js
I think, it's also a PowerPC architecture wise as /proc/cpuinfo states the following:

processor   : 0
cpu     : APM82181
clock       : 800.000008MHz
revision    : 28.131 (pvr 12c4 1c83)
bogomips    : 1600.00
timebase    : 800000008
platform    : PowerPC 44x Platform
model       : amcc,apollo3g
Memory      : 256 MB

I am not that familiar with cross-compiling, so I guess I could compile stuff directly on the device, if there's no binary version I could give a try.
Any advice or recommendation is welcome.

Best regards,
Matthias

I've got a primitive kernel to which I am handcuffed, linux 2.6.21 running on a ppc603 core. I've built v8 and can run the d8 shell on the target system, but now that I've cross-compiled node, it is looking for the standard c library and does not find GLIBC_2.7. I installed a newer library in an alternative location, but the OS ABI is invalid. I think what I need to do is build node with the library included (static linking?), but thought I'd done that. Any thoughts?

Note, I've made changes to deps/v8ppc to bring in the g4compat changes and everything builds without complaint.
git status gives: On branch v0.10.38-release-ppc

I'm trying to compile and use node on a Freescale p1010rdb development board with a e500v2. I have successfully compiled version 0.10.21-release-ppc without any problems, but i have an "illegal instruction" error when i try to execute node.

Tracing the error on gdb gives me the following output:

(gdb) x/20i $pc-32
0x48136b0c: .long 0xc8e40003
0x48136b10: srawi r10,r3,1
0x48136b14: addi r1,r1,-8
0x48136b18: srawi r0,r10,31
0x48136b1c: stw r0,0(r1)
0x48136b20: stw r10,4(r1)
0x48136b24: .long 0xc8c10000
0x48136b28: addi r1,r1,8
=> 0x48136b2c: .long 0xfcc0369c
0x48136b30: .long 0xff873000
0x48136b34: bso- cr7,0x48136b58
0x48136b38: beq- cr7,0x48136b48
0x48136b3c: blt- cr7,0x48136b50
0x48136b40: li r3,1
0x48136b44: blr
0x48136b48: li r3,0
0x48136b4c: blr
0x48136b50: li r3,-1
0x48136b54: blr
0x48136b58: li r3,-1

After some researches, i found out that this instruction should be fcfid (used in deps/v8ppc/src/ppc/code-stubs-ppc.cc), and from what i know e500 doesn't support floating point instructions like fcfid or fctid.

[email protected] install /u/slbld/node/lib/node_modules/sqlite3
node-pre-gyp install --fallback-to-build

node-pre-gyp ERR! Tried to download(403): https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v3.1.8/node-v14-os390-s390x.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for [email protected] and [email protected] (node-v14 ABI) (falling back to source compile with node-gyp)
make: Entering directory '/u/slbld/node/lib/node_modules/sqlite3/build'
ACTION deps_sqlite3_gyp_action_before_build_target_unpack_sqlite_dep Release/obj/gen/sqlite-autoconf-3150000/sqlite3.c
Traceback (most recent call last):
File "./extract.py", line 7, in
tfile = tarfile.open(tarball,'r:gz');
File "/u/slbld/python-2.7.6/lib/python2.7/tarfile.py", line 1678, in open
return func(name, filemode, fileobj, **kwargs)
File "/u/slbld/python-2.7.6/lib/python2.7/tarfile.py", line 1719, in gzopen
raise CompressionError("gzip module is not available")
tarfile.CompressionError: gzip module is not available
deps/action_before_build.target.mk:13: recipe for target 'Release/obj/gen/sqlite-autoconf-3150000/sqlite3.c' failed
make: *** [Release/obj/gen/sqlite-autoconf-3150000/sqlite3.c] Error 1
make: Leaving directory '/u/slbld/node/lib/node_modules/sqlite3/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/u/slbld/node/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack at ChildProcess.emit (events.js:110:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:1078:12)
gyp ERR! System Öâaóùð òôKðð
gyp ERR! command "/u/slbld/node/bin/node" "/u/slbld/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/u/slbld/node/lib/node_modules/sqlite3/lib/binding/node-v14-os390-s390x/node_sqlite3.node" "--module_name=node_sqlite3" "--module_path=/u/slbld/node/lib/node_modules/sqlite3/lib/binding/node-v14-os390-s390x"
gyp ERR! cwd /u/slbld/node/lib/node_modules/sqlite3
gyp ERR! node -v v0.12.17
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/u/slbld/node/bin/node /u/slbld/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/u/slbld/node/lib/node_modules/sqlite3/lib/binding/node-v14-os390-s390x/node_sqlite3.node --module_name=node_sqlite3 --module_path=/u/slbld/node/lib/node_modules/sqlite3/lib/binding/node-v14-os390-s390x' (1)
node-pre-gyp ERR! stack at ChildProcess. (/u/slbld/node/lib/node_modules/sqlite3/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:110:17)
node-pre-gyp ERR! stack at maybeClose (child_process.js:1019:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:1091:5)
node-pre-gyp ERR! System Öâaóùð òôKðð
node-pre-gyp ERR! command "node" "/u/slbld/node/lib/node_modules/sqlite3/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /u/slbld/node/lib/node_modules/sqlite3
node-pre-gyp ERR! node -v v0.12.17
node-pre-gyp ERR! node -v v0.6.31
node-pre-gyp ERR! not ok
Failed to execute '/u/slbld/node/bin/node /u/slbld/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/u/slbld/node/lib/node_modules/sqlite3/lib/binding/node-v14-os390-s390x/node_sqlite3.node --module_name=node_sqlite3 --module_path=/u/slbld/node/lib/node_modules/sqlite3/lib/binding/node-v14-os390-s390x' (1)
npm ERR! Öâaóùð òôKðð
npm ERR! argv "/u/slbld/node/bin/node" "/u/slbld/node/bin/npm" "install" "-g" "sqlite3"
npm ERR! node v0.12.17
npm ERR! npm v2.15.1
npm ERR! code ELIFECYCLE

npm ERR! [email protected] install: node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! This is most likely a problem with the sqlite3 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-pre-gyp install --fallback-to-build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs sqlite3
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR! npm owner ls sqlite3
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /u/slbld/npm-debug.log

os.release(); will return '1' on AIX 6.1

On Linux systems we get back the same answer as uname -r

The documentation http://nodejs.org/api/os.html#os_os_release claims to run the operating system release. (it appears to be open to interpretation)

The test crashes when executed with --stack-size=128 when it should have thrown and handled a stack overflow error.

The failing output is:
FATAL ERROR: CALL_AND_RETRY Allocation failed - process out of memory

This is usually followed by a "core dumped" message.

Nice work on v8 and node.js. Thanks! But I ran into a compile error on node (RHEL 6.5 zLinux system). Maybe I'm building it wrong (not sure we want '-m31')?

1. Get the v8 javascript for System z
   mkdir ~/src
   cd ~/src
   git clone https://github.com/andrewlow/v8z.git
   ...
2. Build it:
   cd v8z/
   make dependencies; make s390x
   ...
3. Get the node.js for system z:
   git clone https://github.com/andrewlow/node.git
4. Build it:
   cd node
   ./configure
   ...
   make
   ...
   g++ -pthread -rdynamic -m31 -m31 -o /root/src/node/out/Release/mksnapshot -Wl,--start-group /root/src/node/out/Release/obj.host/mksnapshot/deps/v8z/src/mksnapshot.o /root/src/node/out/Release/obj.host/deps/v8z/tools/gyp/libv8_base.a /root/src/node/out/Release/obj.host/deps/v8z/tools/gyp/libv8_nosnapshot.a -Wl,--end-group
   /usr/bin/ld: crt1.o: No such file: No such file or directory
   collect2: ld returned 1 exit status
   make[1]: *** [/root/src/node/out/Release/mksnapshot] Error 1
   make[1]: Leaving directory `/root/src/node/out'

I'm using Python 2.6.2 on an AIX 6.1 system. Since my system does not have the shared libraries libstdc++.a(libstdc++.so.6) and libgcc_s.a(shr.o) installed I'm trying to compile node.js v0.10.26-release.

Unfortunately the configuration script does not work out of the box for me. Error message:

Traceback (most recent call last):
File "./configure", line 673, in
configure_node(output)
File "./configure", line 493, in configure_node
cc_version, is_clang = compiler_version()
File "./configure", line 434, in compiler_version
except WindowsError:
NameError: global name 'WindowsError' is not defined

The following solution worked for me: Replacing 'WindowsError' by 'OSError' in the configure script. The Error Class 'WindowsError' seems not to be known in Linux environments (also tested the variable existence in Ubuntu 12.04).

Another minor problem was that I needed to set the compiler manually to gcc by calling make with the parameter "CC=gcc"

Now the configure script works fine for me. I will post a further compilation problem in another issue report. Would be glad if someone could help me with that problem.

Simple test case test/simple/test-crypto-random.js fails thus:

FATAL ERROR: node::RandomBytesRequest() Out of Memory

Three test cases fail with the exceptions:

test-fs-readfile-error.js
AssertionError: null == true
at /home/gireesh/aix/node.nnew/node/test/simple/test-fs-readfile-error.js:34:5
at ChildProcess.exithandler (child_process.js:635:7)
at ChildProcess.EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:735:16)
at Socket. (child_process.js:948:11)
at Socket.EventEmitter.emit (events.js:95:17)
at Pipe.close (net.js:466:12)

test-fs-readfile-pipe.js:

AssertionError: it exits normally
at /home/gireesh/aix/node.nnew/node/test/simple/test-fs-readfile-pipe.js:51:3
at ChildProcess.exithandler (child_process.js:641:7)
at ChildProcess.EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:735:16)
at Socket. (child_process.js:948:11)
at Socket.EventEmitter.emit (events.js:95:17)
at Pipe.close (net.js:466:12)

test-fs-watch.js:

Error: watch ENOSYS
at errnoException (fs.js:1019:11)
at FSWatcher.start (fs.js:1051:11)
at Object.fs.watch (fs.js:1076:11)
at assert.doesNotThrow.fs.watch.renameEv (/home/gireesh/aix/node.nnew/node/test/simple/test-fs-watch.js:65:24)
at Function._throws (assert.js:290:5)
at Function.assert.doesNotThrow (assert.js:321:11)
at Object. (/home/gireesh/aix/node.nnew/node/test/simple/test-fs-watch.js:63:8)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
On the face of it, the issues are due the lack of file system watch facility in AIX.

Two test cases fail with similar errors:

test-cluster-master-error.js

bash-4.2$ ./node test/simple/test-cluster-master-error.js

assert.js:92
throw new assert.AssertionError({
^
AssertionError: The workers did not die after an error in the master
at process. (/home/gireesh/aix/node/test/simple/test-cluster-master-error.js:137:12)
at process.g (events.js:180:16)
at process.EventEmitter.emit (events.js:117:20)

test-cluster-master-kill.js:

bash-4.2$ ./node test/simple/test-cluster-master-kill.js

assert.js:92
throw new assert.AssertionError({
^
AssertionError: worker was alive after master died
at process. (/home/gireesh/aix/node/test/simple/test-cluster-master-kill.js:95:12)
at process.g (events.js:180:16)
at process.EventEmitter.emit (events.js:117:20)

Error:
Assertion failed: __EX, file ../src/cares_wrap.cc, line 818

Steps to reproduce:
./node test/simple/test-http.js

In deps/npm/lib/utils/lifecycle.js is states:
windows calls it's path "Path" usually, but this is not guaranteed.

That pieces of javascript makes allowances when setting the PATH variable, specifically it looks at the way it is capitalised in the environment, and then uses that capitalisation.

We should make a similar modification to NPM's run.js

/u/slbld>npm install -g strongloop
npm ERR! cb() never called!
:/u/slbld>node -v
v0.12.17
:/u/slbld>npm -v
2.15.1

machine: slbld@zoscan2d

This is a blocking issue for trying out strongloop.

Could you please provide binaries of node.js for Mac OS X 10.5 PPC or at least provide a guide on how to easily build it? I have a PowerBook G4 and Xcode 3.14. Thanks!

The simple test case test-vm-timeout.js asserts in deps/uv/src/unix/core.c

bash-4.2$ ./node test/simple/test-vm-timeout.js
IOT/Abort trap (core dumped)

Failing stack found in deubg mode is:

0 0xd050adf4 in pthread_kill () from /usr/lib/libpthreads.a(shr_xpg5.o)
1 0xd050a24c in _p_raise () from /usr/lib/libpthreads.a(shr_xpg5.o)
2 0xd0137284 in raise () from /usr/lib/libc.a(shr.o)
3 0xd01c0d68 in abort () from /usr/lib/libc.a(shr.o)
4 0xd018f8b8 in __assert_c99 () from /usr/lib/libc.a(shr.o)
5 0x102f0654 in uv__close (fd=2) at ../deps/uv/src/unix/core.c:422
6 0x10301ef0 in uv__signal_loop_cleanup (loop=0x203113c8) at ../deps/uv/src/unix/signal.c:246
7 0x1030b374 in uv__loop_delete (loop=0x203113c8) at ../deps/uv/src/unix/loop.c:134
8 0x1030ad98 in uv_loop_delete (loop=0x203113c8) at ../deps/uv/src/unix/loop.c:65
9 0x10b5ba68 in node::Watchdog::Destroy (this=0x2ff22470) at ../src/node_watchdog.cc:72
10 0x10b5b924 in node::Watchdog::~Watchdog (this=0x2ff22470) at ../src/node_watchdog.cc:50
11 0x1010f008 in node::ContextifyScript::EvalMachine (env=0x202acf78, timeout=1000, display_errors=32646760, args=0x2ff2260c, try_catch=0x2ff22590)
at ../src/node_contextify.cc:585
12 0x1010e2c0 in node::ContextifyScript::RunInThisContext (args=0x2ff2260c) at ../src/node_contextify.cc:465
13 0x92158ab0 in ?? ()

Error:

assert.js:92
throw new assert.AssertionError({
^
AssertionError: false == true
at process. (/scratch/jenkins/workspace/github-node-aix-ppc-32-test/test/simple/test-child-process-detached.js:37:3)
at process.EventEmitter.emit (events.js:117:20)

Steps to reproduce:

./node test/simple/test-child-process-detached.js

When building native addons for npm modules, the build script fails in the following manner:

SOLINK_MODULE(target) Release/obj.target/bson.node
Traceback (most recent call last):
File "./gyp-flock-tool", line 50, in
sys.exit(main(sys.argv[1:]))
File "./gyp-flock-tool", line 19, in main
executor.Dispatch(args)
File "./gyp-flock-tool", line 30, in Dispatch
getattr(self, method)(args[1:])
File "./gyp-flock-tool", line 45, in ExecFlock
fcntl.fcntl(fd, fcntl.F_SETLK, op)
IOError: [Errno 22] Invalid argument
gmake: ** [Release/obj.target/bson.node] Error 1

The test case fail with the exception:

bash-4.2$ ./node test/simple/test-abort-fatal-error.js

assert.js:92
throw new assert.AssertionError({
^
AssertionError: null == true
at /home/gireesh/aix/node/test/simple/test-abort-fatal-error.js:38:3
at ChildProcess.exithandler (child_process.js:641:7)
at ChildProcess.EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:743:16)
at Process.ChildProcess._handle.onexit (child_process.js:810:5)
bash-4.2$

Recreated using simple shell command based scenarios:

bash-4.2$ cat abort.c
int main()
{
abort();
}

/bin/sh -c "./a.out > /dev/null 2>&1" | grep Abort

Output seen in linux:
/bin/sh: line 1: 3538 Aborted (core dumped) ./a.out > /dev/null 2>&1
No output seen in aix.
1.

Linux:

bash-4.1$ /bin/sh -c "./a.out > /dev/null 2>&1" > 7 2>&1
bash-4.1$ cat 7
/bin/sh: line 1: 3552 Aborted (core dumped) ./a.out > /dev/null 2>&1

AIX:

bash-4.2$ /bin/sh -c "./a.out > /dev/null 2>&1" > 7 2>&1
IOT/Abort trap (core dumped)
bash-4.2$ cat 7
bash-4.2$

:/u/slbld>npm install -g loopback-connector-soap
npm WARN engine [email protected]: wanted: {"node":">= 4"} (current: {"node":"0.12.17","npm":"2.15.1"})
npm WARN deprecated [email protected]: use uuid module instead
npm WARN engine [email protected]: wanted: {"node":">=4.0"} (current: {"node":"0.12.17","npm":"2.15.1"})

[email protected] install /u/slbld/node/lib/node_modules/loopback-connector-soap/node_modules/strong-soap/node_modules/ursa
node-gyp rebuild

make: Entering directory '/u/slbld/node/lib/node_modules/loopback-connector-soap/node_modules/strong-soap/node_modules/ursa/build'
CXX(target) Release/obj.target/ursaNative/src/ursaNative.o
CCN0465(W) "MAKEDEP" requires at most "0" sub-option(s) to be specified. "1" were given.
"../node_modules/nan/nan_implementation_12_inl.h", line 127.61: CCN5216 (W) An expression of type "void (*)(const FunctionCallbackInfov8::Value &)" cannot be converted to type "void ".
"../node_modules/nan/nan_implementation_12_inl.h", line 99.59: CCN5216 (W) An expression of type "void ()(const FunctionCallbackInfov8::Value &)" cannot be converted to type "void ".
"../node_modules/nan/nan.h", line 1926.50: CCN5216 (W) An expression of type "void ()(Localv8::String, const PropertyCallbackInfov8::Value &)" cannot be converted to type "void ".
"../node_modules/nan/nan.h", line 1931.52: CCN5216 (W) An expression of type "void ()(Localv8::String, Localv8::Value, const PropertyCallbackInfo &)" cannot be converted to type "void ".
"../node_modules/nan/nan.h", line 1969.50: CCN5216 (W) An expression of type "void ()(Localv8::String, const PropertyCallbackInfov8::Value &)" cannot be converted to type "void ".
"../node_modules/nan/nan.h", line 1978.52: CCN5216 (W) An expression of type "void ()(Localv8::String, Localv8::Value, const PropertyCallbackInfo &)" cannot be converted to type "void ".
"../node_modules/nan/nan.h", line 2027.50: CCN5216 (W) An expression of type "void ()(Localv8::String, const PropertyCallbackInfov8::Value &)" cannot be converted to type "void ".
"../node_modules/nan/nan.h", line 2032.52: CCN5216 (W) An expression of type "void ()(Localv8::String, Localv8::Value, const PropertyCallbackInfov8::Value &)" cannot be converted to type "void ".
"../node_modules/nan/nan.h", line 2038.52: CCN5216 (W) An expression of type "void ()(Localv8::String, const PropertyCallbackInfov8::Integer &)" cannot be converted to type "void ".
"../node_modules/nan/nan.h", line 2044.52: CCN5216 (W) An expression of type "void ()(Localv8::String, const PropertyCallbackInfov8::Boolean &)" cannot be converted to type "void ".
"../node_modules/nan/nan.h", line 2050.52: CCN5216 (W) An expression of type "void ()(const PropertyCallbackInfov8::Array &)" cannot be converted to type "void ".
"../node_modules/nan/nan.h", line 2097.50: CCN5216 (W) An expression of type "void ()(unsigned int, const PropertyCallbackInfov8::Value &)" cannot be converted to type "void ".
"../node_modules/nan/nan.h", line 2102.52: CCN5216 (W) An expression of type "void ()(unsigned int, Localv8::Value, const PropertyCallbackInfov8::Value &)" cannot be converted to type "void ".
"../node_modules/nan/nan.h", line 2108.52: CCN5216 (W) An expression of type "void ()(unsigned int, const PropertyCallbackInfov8::Integer &)" cannot be converted to type "void ".
"../node_modules/nan/nan.h", line 2114.52: CCN5216 (W) An expression of type "void ()(unsigned int, const PropertyCallbackInfov8::Boolean &)" cannot be converted to type "void ".
"../node_modules/nan/nan.h", line 2120.52: CCN5216 (W) An expression of type "void ()(const PropertyCallbackInfov8::Array &)" cannot be converted to type "void ".
"../node_modules/nan/nan.h", line 2153.50: CCN5216 (W) An expression of type "void ()(const FunctionCallbackInfov8::Value &)" cannot be converted to type "void ".
"../node_modules/nan/nan.h", line 2175.50: CCN5216 (W) An expression of type "void ()(const FunctionCallbackInfov8::Value &)" cannot be converted to type "void *".
"/u/slbld/.node-gyp/0.12.17/include/node/uv.h", line 1488.16: CCN6410 (W) The function "uv_tty_set_mode" specified in "pragma export" is not uniquely identified. The pragma is ignored.
SOLINK_MODULE(target) Release/obj.target/ursaNative.node
IEW2456E 9207 SYMBOL __dl__Q2_3NanEI20EscapableHandleScopeFPvUl UNRESOLVED.
MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
IEW2456E 9207 SYMBOL __dl__Q2_3NanEI11HandleScopeFPvUl UNRESOLVED. MEMBER
COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
FSUM3065 The LINKEDIT step ended with return code 8.
ursaNative.target.mk:123: recipe for target 'Release/obj.target/ursaNative.node' failed
make: *** [Release/obj.target/ursaNative.node] Error 3
make: Leaving directory '/u/slbld/node/lib/node_modules/loopback-connector-soap/node_modules/strong-soap/node_modules/ursa/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/u/slbld/node/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack at ChildProcess.emit (events.js:110:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:1078:12)
gyp ERR! System Öâaóùð òôKðð
gyp ERR! command "node" "/u/slbld/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /u/slbld/node/lib/node_modules/loopback-connector-soap/node_modules/strong-soap/node_modules/ursa
gyp ERR! node -v v0.12.17
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok
npm WARN optional dep failed, continuing [email protected]
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/apiconnect-cli-util requires async@'1.5.1' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/async,
npm WARN unmet dependency which is version 1.5.2
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/apiconnect-cli-util requires bluebird@'^1.x' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/bluebird,
npm WARN unmet dependency which is version 3.4.6
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/apiconnect-cli-util requires lodash@'4.0.x' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/lodash,
npm WARN unmet dependency which is version 4.16.5
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/generator-loopback requires request@'^2.60.0' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/request,
npm WARN unmet dependency which is version 2.55.0
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/pug-lexer requires is-expression@'^3.0.0' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/is-expression,
npm WARN unmet dependency which is version 2.1.0
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/apiconnect-assembly requires angular-marked@'0.x' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/angular-marked,
npm WARN unmet dependency which is version 1.2.2
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/apiconnect-assembly requires angular-native-dragdrop@'1.1.2' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/angular-native-dragdrop,
npm WARN unmet dependency which is version 1.2.2
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/apiconnect-assembly requires angular-ui-validate@'1.2.1' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/angular-ui-validate,
npm WARN unmet dependency which is version 1.2.2
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/apiconnect-assembly requires glob@'^7.0.3' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/glob,
npm WARN unmet dependency which is version 6.0.4
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/apiconnect-assembly requires tv4@'^1.2.7' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/tv4,
npm WARN unmet dependency which is version 1.1.12
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/apiconnect-cli-login-bluemix requires apiconnect-cli-config@'^2.x' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/apiconnect-cli-config,
npm WARN unmet dependency which is version 3.0.1
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/apiconnect-collective-jmx requires async@'^2.0.1' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/async,
npm WARN unmet dependency which is version 1.5.2
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/apiconnect-collective-jmx requires lodash@'^3.10.1' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/lodash,
npm WARN unmet dependency which is version 4.16.5
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/apiconnect-collective-jmx requires request@'^2.65.0' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/request,
npm WARN unmet dependency which is version 2.55.0
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/loopback requires async@'^2.0.1' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/async,
npm WARN unmet dependency which is version 1.5.2
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/loopback requires underscore.string@'^3.0.3' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/underscore.string,
npm WARN unmet dependency which is version 2.3.3
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/loopback-datasource-juggler requires async@'~1.0.0' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/async,
npm WARN unmet dependency which is version 1.5.2
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/loopback-datasource-juggler requires qs@'^3.1.0' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/qs,
npm WARN unmet dependency which is version 6.3.0
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/microgateway requires apiconnect-cli-config@'^2.x' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/apiconnect-cli-config,
npm WARN unmet dependency which is version 3.0.1
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/microgateway requires express-session@'^1.13.0' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/express-session,
npm WARN unmet dependency which is version 1.11.3
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/microgateway requires fs-extra@'^0.30.0' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/fs-extra,
npm WARN unmet dependency which is version 0.26.7
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/microgateway requires glob@'^7.0.3' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/glob,
npm WARN unmet dependency which is version 6.0.4
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/microgateway requires js-yaml@'^3.5.2' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/js-yaml,
npm WARN unmet dependency which is version 3.4.6
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/microgateway requires request@'^2.69.0' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/request,
npm WARN unmet dependency which is version 2.55.0
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/microgateway requires semver@'^4.1.0' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/semver,
npm WARN unmet dependency which is version 5.3.0
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/swagger-ui requires swagger-client@'2.0.36' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/swagger-client,
npm WARN unmet dependency which is version 2.1.23
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/swagger-ui requires handlebars@'~1.0.10' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/handlebars,
npm WARN unmet dependency which is version 4.0.5
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/swagger-ui requires less@'~1.4.2' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/less,
npm WARN unmet dependency which is version 2.7.1
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/apiconnect-collective-controller-api requires request@'^2.69.0' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/request,
npm WARN unmet dependency which is version 2.55.0
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/apim-ui requires glob@'^7.0.3' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/glob,
npm WARN unmet dependency which is version 6.0.4
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/apim-ui requires js-yaml@'^3.6.0' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/js-yaml,
npm WARN unmet dependency which is version 3.4.6
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/apim-ui requires request@'^2.69.0' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/request,
npm WARN unmet dependency which is version 2.55.0
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/apim-ui requires tv4@'^1.2.7' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/tv4,
npm WARN unmet dependency which is version 1.1.12
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/json-schema-generator/node_modules/request/node_modules/hawk requires hoek@'0.9.x' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/hoek,
npm WARN unmet dependency which is version 2.16.3
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/json-schema-generator/node_modules/request/node_modules/hawk requires boom@'0.4.x' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/boom,
npm WARN unmet dependency which is version 2.10.1
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/json-schema-generator/node_modules/request/node_modules/hawk requires cryptiles@'0.2.x' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/cryptiles,
npm WARN unmet dependency which is version 2.0.5
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/json-schema-generator/node_modules/request/node_modules/hawk requires sntp@'0.2.x' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/sntp,
npm WARN unmet dependency which is version 1.0.9
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/json-schema-generator/node_modules/request/node_modules/bl/node_modules/readable-stream requires isarray@'0.0.1' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/isarray,
npm WARN unmet dependency which is version 1.0.0
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/json-schema-generator/node_modules/request/node_modules/form-data/node_modules/mime-types requires mime-db@'~1.5.0' but will load
npm WARN unmet dependency /u/slbld/node/lib/node_modules/apiconnect/node_modules/mime-db,
npm WARN unmet dependency which is version 1.24.0
[email protected] /u/slbld/node/lib/node_modules/loopback-connector-soap
├── [email protected] ([email protected])
├── [email protected] ([email protected], [email protected], [email protected], forever-agen

Found this while trying to resolve NPM issues.

Build node on Intel & PPC the same way

PPC

./configure --debug --dest-cpu=ppc; make -j20

Intel

./configure --debug --dest-cpu=ia32; make -j7

Now run the following on both.

./node --trace deps/npm/bin/npm-cli.js install url | head -2

Intel output

$ ./node --trace deps/npm/bin/npm-cli.js install url | head -2 1: Instantiate+59(this=0x31f29af9 <JS Object>, 0x31f34711 <FunctionTemplateInfo>, 0x31f08091 <undefined>) { 2: InstantiateFunction+64(this=0x31f29af9 <JS Object>, 0x31f34711 <FunctionTemplateInfo>, 0x31f08091 <undefined>) {

PPC output

$ ./node --trace deps/npm/bin/npm-cli.js install url | head -2 1: Instantiate+88(this=0x9a829ae9 <JS Object>, 0x9a8346e5 <FunctionTemplateInfo>, 0x9a808091 <undefined>) { 2: InstantiateFunction+108(this=0x9a808091 <undefined>, 0x9a8346e5 <FunctionTemplateInfo>, 0x9a808091 <undefined>) {

If you look carefully - you'll notice that the value of this should be <JS Object> but is <undefined> on PPC. I'm sort of surprised anything works.

AIX version fails with ECONNRESET or EPIPE or ECONNREFUSED
Simple test test/simple/test-debugger-client.js fails with one of the following stack:

got stderr data "debugger listening on port 13683\n"

new node process: 12189734
starting debugger session
connecting...

events.js:72
throw er; // Unhandled 'error' event
^
Error: read ECONNRESET
at errnoException (net.js:901:11)
at TCP.onread (net.js:556:19)

new node process: 13566188
starting debugger session
got stderr data "debugger listening on port 13683\n"
connecting...

events.js:72
throw er; // Unhandled 'error' event
^
Error: connect ECONNREFUSED
at errnoException (net.js:901:11)
at Object.afterConnect as oncomplete

got stderr data "debugger listening on port 13683\n"

connecting...
new node process: 12189732
starting debugger session
ready!
requesting version

events.js:72
throw er; // Unhandled 'error' event
^
Error: write EPIPE
at errnoException (net.js:901:11)
at Object.afterWrite (net.js:718:19)

Simple test test/simple/test-dgram-multicast-setTTL.js fails with this call stack:

dgram.js:372
throw errnoException(process._errno, 'setMulticastTTL');
^
Error: setMulticastTTL EINVAL
at errnoException (dgram.js:457:11)
at Socket.setMulticastTTL (dgram.js:372:11)
at Socket. (/home/gireesh/aix/node/test/simple/test-dgram-multicast-setTTL.js:30:10)
at Socket.EventEmitter.emit (events.js:92:17)
at startListening (dgram.js:141:10)
at dgram.js:216:7
at dns.js:72:18
at process._tickCallback (node.js:415:13)
at Function.Module.runMain (module.js:499:11)
at startup (node.js:119:16)

This repository was originally set up by Andrew Low to house a fork of V8 and Node.js with additional changes to build and run on IBM platforms. Eventually this became an official IBM project to maintain ports of Node.js to IBM platforms (https://developer.ibm.com/node/sdk/). Andrew has not been working full time on these ports for over a year but the rest of the team has continued to use this repository.

We are planning to move this repository under https://github.com/ibmruntimes/node following the process documented at https://help.github.com/articles/transferring-a-repository/#transferring-from-a-user-to-an-organization. We expect requests to the old repository should automatically be redirected to the new repository after the move. This should be transparent.

We expect this to be done in approximately a week's time from the raising of this issue, but I will provide a more precise update closer to the time.

Building (in the v8ppc dependency) fails due to the absence of an "elf.h". It appears that this file is expected to exist on all non-AIX systems, but OS X 10.5 does not seem to have it by default.

Is there something I have forgotten to install?

Here is the tail end of my build:

  touch /Users/anovak/build/node/out/Release/obj.target/deps/v8ppc/tools/gyp/js2c.stamp
  g++ '-D_DARWIN_USE_64_BIT_INODE=1' '-DENABLE_DEBUGGER_SUPPORT' '-DENABLE_EXTRA_CHECKS' '-DV8_TARGET_ARCH_PPC' -I../deps/v8ppc/src  -O3 -gdwarf-2 -fstrict-aliasing -mmacosx-version-min=10.5 -arch i386 -Wall -Wendif-labels -W -Wno-unused-parameter -fno-rtti -fno-exceptions -fno-threadsafe-statics -fno-strict-aliasing -MMD -MF /Users/anovak/build/node/out/Release/.deps//Users/anovak/build/node/out/Release/obj.target/v8_base/deps/v8ppc/src/accessors.o.d.raw  -c -o /Users/anovak/build/node/out/Release/obj.target/v8_base/deps/v8ppc/src/accessors.o ../deps/v8ppc/src/accessors.cc
In file included from ../deps/v8ppc/src/macro-assembler.h:64,
                 from ../deps/v8ppc/src/deoptimizer.h:34,
                 from ../deps/v8ppc/src/accessors.cc:32:
../deps/v8ppc/src/ppc/assembler-ppc.h:48:17: error: elf.h: No such file or directory
../deps/v8ppc/src/objects.h:1052: warning: integer overflow in expression
make[1]: *** [/Users/anovak/build/node/out/Release/obj.target/v8_base/deps/v8ppc/src/accessors.o] Error 1
make: *** [node] Error 2
bash-3.2$ 

A change to the path of a file on github required by the npm-test-peer-deps package breaks that test.

+npm install packages/npm-test-peer-deps
2> npm ERR! fetch failed https://raw.github.com/gist/3971128/3f6aa37b4fa1186c2f47da9b77dcc4ec496e3483/index.js
2> npm ERR! Error: 404 Not Found

Issue against NPM:
https://github.com/isaacs/npm/issues/3897

A fix is available to pull as it is not yet in our builds:
runk/npm@243f265

I can't run node.js on PowerPC 440EP, I get only error "Illegal instruction".

Hardware info:

cat /proc/cpuinfo
processor       : 0
cpu             : 440EP Rev. C
clock           : 533.333332MHz
revision        : 24.212 (pvr 4222 18d4)
bogomips        : 1066.66
timebase        : 533333332
platform        : CPU440EP
model           : cpu440
Memory          : 128 MB

LD_SHOW_AUXV=1 /bin/true
AT_DCACHEBSIZE:  0x20
AT_ICACHEBSIZE:  0x20
AT_UCACHEBSIZE:  0x0
AT_SYSINFO_EHDR: 0x100000
AT_HWCAP:        booke mmu fpu ppc32
AT_PAGESZ:       4096
AT_CLKTCK:       100
AT_PHDR:         0x10000034
AT_PHENT:        32
AT_PHNUM:        8
AT_BASE:         0x48000000
AT_FLAGS:        0x0
AT_ENTRY:        0x1000446c
AT_UID:          0
AT_EUID:         0
AT_GID:          0
AT_EGID:         0
AT_SECURE:       0
AT_RANDOM:       0xbf8c04f2
AT_EXECFN:       /bin/true
AT_PLATFORM:     ppc440
AT_BASE_PLATFORM:ppc440

Software info:

I'm using powerpc-440-linux-gnu compiler (version 5.2.0) and Linux v3.6.7.

I tried to use different versions of sources:

*node-0.10-ppc* from https://github.com/ibmruntimes/node
*node-4.x-port* from https://github.com/ibmruntimes/node
*node-v4.4.7* from https://nodejs.org/dist/v4.4.7/node-v4.4.7.tar.gz

I'm using the following script for build of node.js:

#!/bin/bash

CROSS_COMPILER=powerpc-440-linux-gnu
HOST=powerpc-linux
ENDIAN=big
BUILD_PATH=/home/user/node
CFLAGS=-Os
JOBS=4

export ARCH=ppc
export CC=${CROSS_COMPILER}-gcc
export CXX=${CROSS_COMPILER}-g++
export CFLAG=${CFLAGS}
export AR=${CROSS_COMPILER}-ar r
export LINK=${CROSS_COMPILER}-g++

export PATH=${PATH}:/home/user/powerpc-440-linux-gnu/bin

./configure --without-snapshot --prefix=${BUILD_PATH} --dest-cpu=ppc --dest-os=linux

make -j ${JOBS}
make install

• Which version of node.js should I use?
• Do we have working portable
  version of node.js for PowerPC 440EP ?

The test case fail with the exception:

bash-4.2$ ./node test/simple/test-http-upgrade-server.js

assert.js:92
throw new assert.AssertionError({
^
AssertionError: "HTTP/1.1 200" == "0\r\n\r\n"
at Socket. (/home/gireesh/aix/node/test/simple/test-http-upgrade-server.js:160:12)
at Socket.EventEmitter.emit (events.js:95:17)
at Socket. (stream_readable.js:746:14)
at Socket.EventEmitter.emit (events.js:92:17)
at emitReadable (_stream_readable.js:408:10)
at emitReadable (_stream_readable.js:404:5)
at readableAddChunk (_stream_readable.js:165:9)
at Socket.Readable.push (_stream_readable.js:127:10)
at TCP.onread (net.js:526:21)

Recreatable using a simple http server with a client receiving a 'hello' message.

The test passes when run manually, but fails under Jenkins with the following stack:

# assert.js:92
# throw new assert.AssertionError({
# ^
# AssertionError: "ENOTSOCK" == "EINVAL"
# at Server.<anonymous> (test/simple/test-net-listen-fd0.js:34:10)
# at Server.EventEmitter.emit (events.js:95:17)
# at net.js:1043:12
# at process._tickCallback (node.js:415:13)
# at Function.Module.runMain (module.js:499:11)
# at startup (node.js:119:16)
# at node.js:901:3

This seems to be related to the test's use of file descriptor 0 (stdin) and the expectation of a particular error code being hit; under Jenkins a slightly different error code than expected is observed in the failing case.

The failure has been observed on RHEL 6.3 on Intel (32-bit and 64-bit modes) and PowerPC (32-bit mode).

Hi,

I am trying to run node on my e500 ppc. I used -msoft-float option to work around the Illegal Instruction set issue. But now i am hitting the following crash. Appreciate if someone can help me on what is going wrong.

gdb) bt
#0 0x1038007c in v8::Context::Enter() ()
#1 0x1086e8e8 in node::CreateEnvironment(v8::Isolate_, uv_loop_s_, v8::Handlev8::Context, int, char const* const_, int, char const_ const*) ()
#2 0x1086f2a4 in node::Start(int, char**) ()
#3 0x1088b820 in main ()

(gdb) x/20i $pc -16
0x1038006c <_ZN2v87Context5EnterEv+40>: stw r25,20(r1)
0x10380070 <_ZN2v87Context5EnterEv+44>: stw r28,32(r1)
0x10380074 <_ZN2v87Context5EnterEv+48>: stw r29,36(r1)
0x10380078 <_ZN2v87Context5EnterEv+52>: stw r30,40(r1)
=> 0x1038007c <_ZN2v87Context5EnterEv+56>: lwz r9,0(r3)
0x10380080 <_ZN2v87Context5EnterEv+60>: rlwinm r9,r9,0,0,9
0x10380084 <_ZN2v87Context5EnterEv+64>: lwz r11,28(r9)
0x10380088 <_ZN2v87Context5EnterEv+68>: addi r27,r11,-16
0x1038008c <_ZN2v87Context5EnterEv+72>: lwz r30,13692(r27)
0x10380090 <_ZN2v87Context5EnterEv+76>: lwz r24,13632(r27)
0x10380094 <_ZN2v87Context5EnterEv+80>: stw r0,13632(r27)
0x10380098 <_ZN2v87Context5EnterEv+84>: lwz r10,24(r30)
0x1038009c <_ZN2v87Context5EnterEv+88>: lwz r29,20(r30)
0x103800a0 <_ZN2v87Context5EnterEv+92>: lwz r25,0(r3)
0x103800a4 <_ZN2v87Context5EnterEv+96>: cmpw cr7,r10,r29
0x103800a8 <_ZN2v87Context5EnterEv+100>:
bge cr7,0x10380128 <_ZN2v87Context5EnterEv+228>
0x103800ac <_ZN2v87Context5EnterEv+104>: lwz r9,16(r30)
0x103800b0 <_ZN2v87Context5EnterEv+108>: rlwinm r0,r10,2,0,29
0x103800b4 <_ZN2v87Context5EnterEv+112>: addi r11,r10,1
0x103800b8 <_ZN2v87Context5EnterEv+116>: stwx r25,r9,r0

v0.10.47 contained two V8 commits that were ported to deps/v8z in the v0.10-ppc branch. These should also be ported to deps/v8ppc for the Power platforms.

CC @BethGriggs @sxa555

I would be very happy if someone has a solution for my compilation problem. Thank you in advance.

My configuration:
gcc version 4.4.5
GNU Make 3.8.2
AIX 6.1

While compiling node-0.10.26-release-ppc I get the following error lines:
////////////////////////////////
../deps/uv/src/unix/aix.c:59:31: warning: sys/ahafs_evProds.h: No such file or directory
../deps/uv/src/unix/aix.c: In function 'setup_ahafs':
../deps/uv/src/unix/aix.c:671: warning: passing argument 1 of 'file_is_a_directory' discards qualifiers from pointer target type
../deps/uv/src/unix/aix.c:523: note: expected 'char ' but argument is of type 'const char *'
../deps/uv/src/unix/aix.c:685: warning: passing argument 1 of 'mk_subdirs' discards qualifiers from pointer target type
../deps/uv/src/unix/aix.c:629: note: expected 'char *' but argument is of type 'const char *'
../deps/uv/src/unix/aix.c: In function 'parse_data':
../deps/uv/src/unix/aix.c:798: error: 'AHAFS_MODDIR_UNMOUNT' undeclared (first use in this function)
../deps/uv/src/unix/aix.c:798: error: (Each undeclared identifier is reported only once
../deps/uv/src/unix/aix.c:798: error: for each function it appears in.)
../deps/uv/src/unix/aix.c:798: error: 'AHAFS_MODDIR_REMOVE_SELF' undeclared (first use in this function)
../deps/uv/src/unix/aix.c:812: warning: passing argument 1 of 'strdup' from incompatible pointer type
/opt/freeware/lib/gcc/powerpc-ibm-aix6.1.0.0/4.4.5/include-fixed/string.h:210: note: expected 'const char *' but argument is of type 'char ()[1023]'
../deps/uv/src/unix/aix.c:817: error: 'AHAFS_MODFILE_RENAME' undeclared (first use in this function)
../deps/uv/src/unix/aix.c: In function 'uv__ahafs_event':
../deps/uv/src/unix/aix.c:866: warning: comparison between pointer and integer
../deps/uv/src/unix/aix.c:877: warning: comparison between pointer and integer
../deps/uv/src/unix/aix.c:889: warning: passing argument 2 of 'handle->cb' from incompatible pointer type
../deps/uv/src/unix/aix.c:889: note: expected 'const char ' but argument is of type 'char ()[1023]'
../deps/uv/src/unix/aix.c: In function 'uv_fs_event_init':
../deps/uv/src/unix/aix.c:940: warning: comparison between pointer and integer
../deps/uv/src/unix/aix.c:960: warning: passing argument 1 of 'strdup' from incompatible pointer type
/opt/freeware/lib/gcc/powerpc-ibm-aix6.1.0.0/4.4.5/include-fixed/string.h:210: note: expected 'const char ' but argument is of type 'char ()[1023]'
../deps/uv/src/unix/aix.c: In function 'uv__fs_event_close':
../deps/uv/src/unix/aix.c:973: warning: 'return' with a value, in function returning void
../deps/uv/src/unix/aix.c:989: warning: 'return' with a value, in function returning void
make[1]: *** [/opt/mcrm/devel/user/alin/temp/node_js/node-0.10.26-release-ppc/out/Release/obj.target/libuv/deps/uv/src/unix/aix.o] Error 1
make[1]: Leaving directory `/opt/mcrm/devel/user/alin/temp/node_js/node-0.10.26-release-ppc/out'
make: *** [node] Error 2
//////////////////////////////////

I think the problems occur since bos.ahafs is not installed and therefore the header file /usr/include/sys/ahafs_evProds.h is not existing, right?

$ lslpp -f bos.ahafs
lslpp: Fileset bos.ahafs not installed.

Unfortunately I think there is no way to install bos.ahafs on the AIX machine by our clients it-departement so I have to find a another way? I would be happy if anyone has a fix or even a suggestion.

Error:
assert.js:92
throw new assert.AssertionError({
^
AssertionError: false == true
at Object. (/scratch/jenkins/workspace/github-node-aix-ppc-32-test/test/simple/test-executable-path.js:52:8)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:901:3

Steps to reproduce:
./node test/simple/test-executable-path.js

Hi when I try to compile on my Synology DS413 which has a powerpc architecure I get following output. The output is the same when I try to compile the regular v0.10.29-release from the joyent repository.

Any idea how I can fix this?

I hope you can help me out.

DiskStation>git clone -b v0.10.29-release-ppc https://github.com/andrewlow/node.git && cd node/
DiskStation>./configure --prefix=/opt/node
{ 'target_defaults': { 'cflags': [],
                       'default_configuration': 'Release',
                       'defines': [],
                       'include_dirs': [],
                       'libraries': []},
  'variables': { 'clang': 0,
                 'gcc_version': 34,
                 'host_arch': 'ppc',
                 'node_byteorder': 'big',
                 'node_install_npm': 'true',
                 'node_prefix': '/opt/node',
                 'node_shared_cares': 'false',
                 'node_shared_http_parser': 'false',
                 'node_shared_libuv': 'false',
                 'node_shared_openssl': 'false',
                 'node_shared_v8': 'false',
                 'node_shared_zlib': 'false',
                 'node_tag': '',
                 'node_unsafe_optimizations': 0,
                 'node_use_dtrace': 'false',
                 'node_use_etw': 'false',
                 'node_use_openssl': 'true',
                 'node_use_perfctr': 'false',
                 'node_use_systemtap': 'false',
                 'python': '/opt/bin/python2',
                 'target_arch': 'ppc',
                 'v8_enable_gdbjit': 0,
                 'v8_no_strict_aliasing': 1,
                 'v8_use_snapshot': 'true',
                 'visibility': ''}}
creating  ./config.gypi
creating  ./config.mk
Diskstation>make
make -C out BUILDTYPE=Release V=1
make[1]: Entering directory `/volume1/@tmp/node/out'
deps/v8ppc/tools/gyp/v8_base.target.mk:269: warning: overriding recipe for target `/volume1/@tmp/node/out/Release/libv8_base.a'
deps/v8ppc/tools/gyp/v8_base.host.mk:269: warning: ignoring old recipe for target `/volume1/@tmp/node/out/Release/libv8_base.a'
deps/v8ppc/tools/gyp/v8_nosnapshot.target.mk:139: warning: overriding recipe for target `/volume1/@tmp/node/out/Release/libv8_nosnapshot.a'
deps/v8ppc/tools/gyp/v8_nosnapshot.host.mk:143: warning: ignoring old recipe for target `/volume1/@tmp/node/out/Release/libv8_nosnapshot.a'
deps/v8ppc/tools/gyp/v8_snapshot.target.mk:166: warning: overriding recipe for target `/volume1/@tmp/node/out/Release/libv8_snapshot.a'
deps/v8ppc/tools/gyp/v8_snapshot.host.mk:162: warning: ignoring old recipe for target `/volume1/@tmp/node/out/Release/libv8_snapshot.a'
  cc '-D_DARWIN_USE_64_BIT_INODE=1' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-D_GNU_SOURCE' '-DHAVE_CONFIG_H' '-DCARES_STATICLIB' -I../deps/cares/include -I../deps/cares/src -I../deps/cares/config/linux  -Wall -Wextra -Wno-unused-parameter -pthread -m32 -g --std=gnu89 -pedantic -Wall -Wextra -Wno-unused-parameter -O2 -fno-strict-aliasing -fno-tree-sink -fno-omit-frame-pointer  -MMD -MF /volume1/@tmp/node/out/Release/.deps//volume1/@tmp/node/out/Release/obj.target/cares/deps/cares/src/ares_cancel.o.d.raw  -c -o /volume1/@tmp/node/out/Release/obj.target/cares/deps/cares/src/ares_cancel.o ../deps/cares/src/ares_cancel.c
cc1: error: unrecognized command line option "-fno-tree-sink"
make[1]: *** [/volume1/@tmp/node/out/Release/obj.target/cares/deps/cares/src/ares_cancel.o] Error 1
make[1]: Leaving directory `/volume1/@tmp/node/out'
make: *** [node] Error 2

Running npm on z/OS gives the following error npm 2: FSUM7332 syntax error: got (), expecting Word

this is because the npm script has the following line as the location of the node runtime

#!/home/jenkins/workspace/ibmnode-ascii-v0.12-build-zos/install/bin/node

Editting this file to make the first line

#!/usr/bin/env node

allows the npm command to run as expected (providing that node is on the path)

Simple test test/simple/test-http-client-timeout-agent.js fails with this call stack:

assert.js:92
throw new assert.AssertionError({
^
AssertionError: timeout on http request called too much
at process. (/home/gireesh/aix/node/test/simple/test-http-client-timeout-agent.js:95:10)
at process.EventEmitter.emit (events.js:117:20)

I've compiled node 0.11.12-release-ppc on Ubuntu 12.04 on Vagrant on OS X. The target device is a Synology DS413 (NAS). I used the proper cross-compilation toolchain by Synology.
Compilation succeeded only without a snapshot.

The illegal instruction (or SIGILL) occurs when no arguments are given, but never if given -v or -h. I have not gone through all possible CLI argument combinations.

With gdb on the NAS I've tried to locate the point where the SIGILL occurs, but have failed to reach the goal. If I ask for the backtrace right after the SIGILL, this is how it looks:

Program received signal SIGILL, Illegal instruction.
0x33c2f5e0 in ?? ()
(gdb) backtrace
#0 0x33c2f5e0 in ?? ()
#1 0x33c2f1f4 in ?? ()

Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Running gdb I found that there are lots of things done in the 'v8' namespace C++ code which makes me think the v8 that comes with this node.js fork has not been compiled for this CPU - no surprise - and I haven't succeeded in compiling v8ppc for it yet.

To fix this, should I find out if the problem really is in v8 (how?), and therefore compile v8ppc for this CPU, or do something to node?

Hi Andrew,
I'm currently compiling v8ppc on an old debian PPC. For this node fork, do I just follow the instructions on the README? I have a feeling I need to incorporate the v8ppc build somehow?
Thanks
Jaime

In the modifications to support PPC we have a check in the openssl file to see if the target == ppc and if so, we assume it's a big endian platform.

This is wrong if you want to build the PPC simulated version on an Intel (little endian) machine. As openssl is native code, it should be compiled in a mode that works for the host.

The test test/simple/test-debugger-repl-break-in-module.js fails with the below exception

dying badly buffer="debug> debug> "
child is closed
UncaughtException [Error: Timeout. Expected: /break in .[\/]main.js:4/] Error: Timeout. Expected: /break in .[\/]main.js:4/
at ChildProcess. (/home/gireesh/aix/node/test/simple/helper-debugger-repl.js:89:13)
at ChildProcess.EventEmitter.emit (events.js:117:20)
at maybeClose (child_process.js:743:16)
at Process.ChildProcess._handle.onexit (child_process.js:810:5)
Error: Timeout. Expected: /break in .*[\/]main.js:4/
process exit 1

The reason I ask is there at a ton of us left out in the cold on Synology boxes...

Freescale QorIQ to be exact.

https://global.download.synology.com/download/Document/DataSheet/DiskStation/13-year/DS213+/Synology_DS213+_Data_Sheet_enu.pdf

Two scenarios:

1. inline debugger attach:

actual output:

bash-4.2$ ./node debug --debug-brk a.js
< debugger listening on port 5858
connecting... ok
debug>

expected output:

bash-4.2$ ./node debug --debug-brk a.js
< debugger listening on port 5858
connecting... ok
break in a.js:1
1 debugger;
2 var i = 10;
3
debug>

1. late attach:

terminal #1:

actual output:
bash-4.2$ ./node --debug-brk a.js
< debugger listening on port 5858

terminal #2:
bash-4.2$ ./node debug --debug-brk a.js
< debugger listening on port 5858
connecting... ok
debug>

expected output in terminal #2:

bash-4.2$ ./node debug --debug-brk a.js
< debugger listening on port 5858
connecting... ok
break in a.js:1
1 debugger;
2 var i = 10;
3
debug>

Compiled successfully in AIX machine using IBM XL C/C++ compiler. and the command "node -v“ run successfully.

but an error happened when run an simple test case, the details is as following.
content of script example print.js:
console.log('hello world');
using the command: node print.js, the error messages are as following:

fs.js:1267
if (!stat.isSymbolicLink()) {
^
TypeError: Object has no method 'isSymbolicLink'
at Object.realpathSync (fs.js:1267:17)
at tryFile (module.js:142:15)
at Function.Module._findPath (module.js:181:18)
at Function.Module._resolveFilename (module.js:336:25)
at Function.Module._load (module.js:280:25)
at Function.Module.runMain (module.js:497:10)
at startup (node.js:119:16)
at node.js:902:3

This issue occurs in the fs.js file, the codes are following:
fs.realpathSync = function realpathSync(p, cache) {
// make p is absolute
p = pathModule.resolve(p);

if (cache && Object.prototype.hasOwnProperty.call(cache, p)) {
return cache[p];
}

var original = p,
seenLinks = {},
knownHard = {};

// current character position in p
var pos;
// the partial path so far, including a trailing slash if any
var current;
// the partial path without a trailing slash (except when pointing at a root)
var base;
// the partial path scanned in the previous round, with slash
var previous;

start();

function start() {
// Skip over roots
var m = splitRootRe.exec(p);
pos = m[0].length;
current = m[0];
base = m[0];
previous = '';

// On windows, check that the root exists. On unix there is no need.
if (isWindows && !knownHard[base]) {
fs.lstatSync(base);
knownHard[base] = true;
}
}

// walk down the path, swapping out linked pathparts for their real
// values
// NB: p.length changes.
while (pos < p.length) {
// find the next part
nextPartRe.lastIndex = pos;
var result = nextPartRe.exec(p);
previous = current;
current += result[0];
base = previous + result[1];
pos = nextPartRe.lastIndex;

// continue if not a symlink
if (knownHard[base] || (cache && cache[base] === base)) {
continue;
}

var resolvedLink;
if (cache && Object.prototype.hasOwnProperty.call(cache, base)) {
// some known symbolic link. no need to stat again.
resolvedLink = cache[base];
} else {
var stat = fs.lstatSync(base);
if (!stat.isSymbolicLink()) { //Error occurred!!!!!
knownHard[base] = true;
if (cache) cache[base] = base;
continue;
}

// read the link if it wasn't read before
// dev/ino always return 0 on windows, so skip the check.
var linkTarget = null;
if (!isWindows) {
var id = stat.dev.toString(32) + ':' + stat.ino.toString(32);
if (seenLinks.hasOwnProperty(id)) {
linkTarget = seenLinks[id];
}
}
if (linkTarget === null) {
fs.statSync(base);
linkTarget = fs.readlinkSync(base);
}
resolvedLink = pathModule.resolve(previous, linkTarget);
// track this, if given a cache.
if (cache) cache[base] = resolvedLink;
if (!isWindows) seenLinks[id] = linkTarget;
}

// resolve the link, then start over
p = pathModule.resolve(resolvedLink, p.slice(pos));
start();
}

if (cache) cache[original] = p;

return p;
};

I have investigate the issue a long time, but I have no idea how to solve it.

who can help me?