Hi.

How do you guys build it on Solaris ? Because I'm stuck. I have a Solaris 
10 server and I need to put a node.js on it. First of all I tried to build 
it with default gcc 3.4.x. After fixing most of the python tools errors (I 
really miss the autotools), adding various --std=c99 and -D_XPG6 flags I 
got in the end:

[...]
g++ '-DSUNOS_NO_IFADDRS' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' 
'-DENABLE_DEBUGGER_SUPPORT' '-DV8_TARGET_ARCH_IA32' '-D__C99FEATURES__=1' 
-I../deps/v8/src  -Wall -m32 -pthreads -fno-strict-aliasing -m32 -O2 
-fno-strict-aliasing -ffunction-sections -fdata-sections -g 
-fno-omit-frame-pointer -fno-rtti -fno-exceptions -MMD -MF 
/home/emz/src/node-v0.8.16/out/Release/.deps//home/emz/src/node-v0.8.16/out/Release/obj.target/v8_base/deps/v8/src/elements-kind.o.d.raw
 
 -c -o 
/home/emz/src/node-v0.8.16/out/Release/obj.target/v8_base/deps/v8/src/elements-kind.o
 
../deps/v8/src/elements-kind.cc
In file included from ../deps/v8/src/elements.h:32,
                 from ../deps/v8/src/objects-inl.h:38,
                 from ../deps/v8/src/v8.h:60,
                 from ../deps/v8/src/api.h:31,
                 from ../deps/v8/src/elements-kind.cc:30:
../deps/v8/src/objects.h:1006: warning: integer overflow in expression
../deps/v8/src/elements-kind.cc: In function `v8::internal::ElementsKind 
v8::internal::GetInitialFastElementsKind()':
../deps/v8/src/elements-kind.cc:44: internal compiler error: in 
c_expand_expr, at c-common.c:4138
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
gmake[1]: *** 
[/home/emz/src/node-v0.8.16/out/Release/obj.target/v8_base/deps/v8/src/elements-kind.o]
 
Error 1
gmake[1]: Leaving directory `/home/emz/src/node-v0.8.16/out'
gmake: *** [node] Error 2

I guess nobody is interested in fixing long ago rested in piece GCC 3.x. I 
tried to build node.js with a Sun Studio (nowdays Oracle Studio) complier 
but it seems like python tools expect GCC only.

So... I tried to build a newer 0.9.x branch. After doing same stufff 
(adding a couple of --std=c99 and -D_XPG6 flags to some .mk and .gyp) I got 
the following issue:

/usr/sfw/bin/gcc '-DSUNOS_NO_IFADDRS' '-D_LARGEFILE_SOURCE' 
'-D_FILE_OFFSET_BITS=64' '-D_GNU_SOURCE' '-DHAVE_CONFIG_H' 
'-D__EXTENSIONS__' '-D_XOPEN_SOURCE=500' '-D_XPG6' -I../deps/uv/include 
-I../deps/uv/include/uv-private -I../deps/uv/src  -pthreads -Wall -Wextra 
-Wno-unused-parameter -m32 -pthreads -g --std=c99 -pedantic -Wall -Wextra 
-Wno-unused-parameter -O2 -fno-strict-aliasing -ffunction-sections 
-fdata-sections -g -fno-omit-frame-pointer  -MMD -MF 
/home/emz/src/node-v0.9.4/out/Release/.deps//home/emz/src/node-v0.9.4/out/Release/obj.target/libuv/deps/uv/src/unix/sunos.o.d.raw
 
 -c -o 
/home/emz/src/node-v0.9.4/out/Release/obj.target/libuv/deps/uv/src/unix/sunos.o 
../deps/uv/src/unix/sunos.c
../deps/uv/src/unix/sunos.c: In function `uv__platform_loop_init':
../deps/uv/src/unix/sunos.c:67: error: structure has no member named `fs_fd'
../deps/uv/src/unix/sunos.c: In function `uv__platform_loop_delete':
../deps/uv/src/unix/sunos.c:80: error: structure has no member named `fs_fd'
../deps/uv/src/unix/sunos.c:81: error: structure has no member named `fs_fd'
../deps/uv/src/unix/sunos.c:82: error: structure has no member named `fs_fd'
gmake[1]: *** 
[/home/emz/src/node-v0.9.4/out/Release/obj.target/libuv/deps/uv/src/unix/sunos.o]
 
Error 1
gmake[1]: Leaving directory `/home/emz/src/node-v0.9.4-patched/out'
gmake: *** [node] Error 2

My C skills are really low, but I didn't find any traces of the fs_ds in 
the uv_loop_t struct.

Can you guys help me with it ?
Thanks.

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Reply via email to