-
Notifications
You must be signed in to change notification settings - Fork 290
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build failure #1237
Comments
@deutschluz - are you building it for the first time, or been doing it for a while and start failing for a specific nightly?
|
heres output of gcc -v: Using built-in specs. |
here s edited output of make -V; i edited because its alot: cc '-DDSO_DLFCN' '-DHAVE_DLFCN_H' '-DNDEBUG' '-DOPENSSL_THREADS' '-DOPENSSL_NO_DYNAMIC_ENGINE' '-DOPENSSL_PIC' '-DOPENSSL_BN_ASM_PART_WORDS' '-DOPENSSL_IA32_SSE2' '-DOPENSSL_BN_ASM_MONT' '-DOPENSSL_BN_ASM_GF2m' '-DSHA1_ASM' '-DSHA256_ASM' '-DSHA512_ASM' '-DRC4_ASM' '-DMD5_ASM' '-DRMD160_ASM' '-DAES_ASM' '-DVPAES_ASM' '-DWHIRLPOOL_ASM' '-DGHASH_ASM' '-DECP_NISTZ256_ASM' '-DPADLOCK_ASM' '-DPOLY1305_ASM' '-DOPENSSLDIR="/etc/ssl"' '-DENGINESDIR="/dev/null"' '-DTERMIOS' -I../deps/openssl/openssl -I../deps/openssl/openssl/include -I../deps/openssl/openssl/crypto -I../deps/openssl/openssl/crypto/include -I../deps/openssl/openssl/crypto/modes -I../deps/openssl/config -I../deps/openssl/config/archs/linux-elf/asm/include -I../deps/openssl/openssl/include -pthread -Wall -Wextra -Wno-unused-parameter -m32 -Wall -O3 -pthread -DL_ENDIAN -fomit-frame-pointer -Wno-missing-field-initializers -Wno-old-style-declaration -O3 -fno-omit-frame-pointer -MMD -MF /home/user/Projects/git/node/out/Release/.deps//home/user/Projects/git/node/out/Release/obj.target/openssl-cli/deps/openssl/openssl/apps/x509.o.d.raw -c -o /home/user/Projects/git/node/out/Release/obj.target/openssl-cli/deps/openssl/openssl/apps/x509.o ../deps/openssl/openssl/apps/x509.c |
3 comments: first i didnt notice till i was cut n pasting, but the compiler used by make changes from gcc to g++; second, all errors seem to come from openssl; third, here is a termbin address with all output of make: http://termbin.com/3z04; its good for 1 month. |
my guess is i will have to change the openssl version to the more recent git repo and try to make again. |
definitions of all the undefined symbols were wrapped in
that makes me to believe that the C and C++ compiler selection might have got cluttered. Can you see if #ls -lrt `which cc`
lrwxr-xr-x 1 root wheel 5 Aug 14 2017 /usr/bin/cc -> clang
#ls -lrt `which c++`
lrwxr-xr-x 1 root wheel 7 Aug 14 2017 /usr/bin/c++ -> clang++
# |
No, openssl source is bundled in the compatible node source, under default configurations. So that change is not necessary. |
@gireeshpunathil oh thats interesting! lrwxrwxrwx 1 root root 3 Apr 26 16:10 cc -> gcc and the command c++ is NOT symlinked to g++. but output of g++ and c++ -v is equal. So I think they are what should i do next then? symlink c++ to g++? |
Are you sure about that? I have built both the node version of openssl and the latest git version and i succeed in building both but the the node version does not pass 'make test' and the latest one does. |
Yes. I assume (from your latest comment) you did it already, and made the build succeed?
|
@gireeshpunathil after symlinking, its still failing. but i commented about having successfully built two different versions of openssl to suggest the possibility that this build failure might be due nodes build system. |
@gireeshpunathil the build finally got through building openssl but it still failed somewhere else. i used a different sequence of build commands. I did 'config' in the dir: /deps/openssl, which is NOT the actual openssl tarball. Then i went back to git/node and did: '/configure'; 'make -j2'. here's the last make command and error output: g++ -pthread -rdynamic -m32 -Wl,--whole-archive,/home/user/Projects/git/node/out/Release/obj.target/libnode.a -Wl,--no-whole-archive -Wl,--whole-archive,/home/user/Projects/git/node/out/Release/obj.target/deps/zlib/libzlib.a -Wl,--no-whole-archive -Wl,--whole-archive,/home/user/Projects/git/node/out/Release/obj.target/deps/uv/libuv.a -Wl,--no-whole-archive -Wl,-z,noexecstack -Wl,--whole-archive /home/user/Projects/git/node/out/Release/obj.target/deps/v8/gypfiles/libv8_base.a -Wl,--no-whole-archive -Wl,--whole-archive,/home/user/Projects/git/node/out/Release/obj.target/deps/openssl/libopenssl.a -Wl,--no-whole-archive -pthread -o /home/user/Projects/git/node/out/Release/node -Wl,--start-group /home/user/Projects/git/node/out/Release/obj.target/node/src/node_main.o /home/user/Projects/git/node/out/Release/obj.target/libnode.a /home/user/Projects/git/node/out/Release/obj.target/deps/v8/gypfiles/libv8_libplatform.a /home/user/Projects/git/node/out/Release/obj.target/tools/icu/libicui18n.a /home/user/Projects/git/node/out/Release/obj.target/deps/zlib/libzlib.a /home/user/Projects/git/node/out/Release/obj.target/deps/http_parser/libhttp_parser.a /home/user/Projects/git/node/out/Release/obj.target/deps/cares/libcares.a /home/user/Projects/git/node/out/Release/obj.target/deps/uv/libuv.a /home/user/Projects/git/node/out/Release/obj.target/deps/nghttp2/libnghttp2.a /home/user/Projects/git/node/out/Release/obj.target/deps/openssl/libopenssl.a /home/user/Projects/git/node/out/Release/obj.target/deps/v8/gypfiles/libv8_base.a /home/user/Projects/git/node/out/Release/obj.target/deps/v8/gypfiles/libv8_libbase.a /home/user/Projects/git/node/out/Release/obj.target/deps/v8/gypfiles/libv8_libsampler.a /home/user/Projects/git/node/out/Release/obj.target/tools/icu/libicuucx.a /home/user/Projects/git/node/out/Release/obj.target/tools/icu/libicudata.a /home/user/Projects/git/node/out/Release/obj.target/tools/icu/libicustubdata.a /home/user/Projects/git/node/out/Release/obj.target/deps/v8/gypfiles/libv8_snapshot.a -ldl -lrt -lm -Wl,--end-group |
i m thinking of resetting and trying to rebuild with new sequence of build command from above and starting a new issue. |
sure, this seems weird to me, so copying @srl295 to gather some insights. |
@deutschluz shouldn't need a new issue, can you just add to this one? @deutschluz can you run:
|
ping @deutschluz |
closing due to inactivity, please re-open if it still an issue |
I just hit this. |
I tried to build nodejs as follows at prompt in git/node dir:
configure
output to gyp files
make -j2
many errors emitted here.
The text was updated successfully, but these errors were encountered: