mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "piranna@gmail.com" <piranna@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Bug on fstat()?
Date: Tue, 26 Aug 2014 21:05:17 +0200	[thread overview]
Message-ID: <CAKfGGh2e5c5n5cnbgN4yuAimTqTATBWUqceGb1ih1=BHFwaiQQ@mail.gmail.com> (raw)
In-Reply-To: <20140825154811.GW12888@brightrain.aerifal.cx>

Sorry for the delay. Ok, I must to say it: the cross-compiler did the
trick :-D I downloaded one of the pre-compiled ones and didn't
understand too much how to use it, so I clone the repository and build
and install it by hand thinking it would help me to understand how it
worked, but didn't :-( Lucklily, I found a Node.js install script from
alpinelinux (http://git.alpinelinux.org/cgit/aports/tree/main/nodejs/APKBUILD)
and a cross-compiler helper script for Parrot AR drone
(https://github.com/felixge/node-cross-compiler/blob/master/platforms/ardrone2.sh)
that gave me some inspiration and I was able to finally compile the
static build :-) I needed to disable OpenSSL support because it gave a
strange error:


  /opt/cross/i686-linux-musl/bin/i686-linux-musl-g++
'-DOPENSSL_NO_SSL2=1' '-DV8_TARGET_ARCH_IA32' '-DENABLE_DISASSEMBLER'
'-DV8_USE_DEFAULT_PLATFORM' -I../deps/v8/src  -pthread -Wall -Wextra
-Wno-unused-parameter -m32 -fno-strict-aliasing -m32 -O3
-ffunction-sections -fdata-sections -fno-tree-vrp
-fno-omit-frame-pointer -fdata-sections -ffunction-sections -O3
-fno-rtti -fno-exceptions -MMD -MF
/home/piranna/Dropbox/Proyectos/NodeOS/NodeOS-QEmu/Layer2-nodejs/deps/node/out/Release/.deps//home/piranna/Dropbox/Proyectos/NodeOS/NodeOS-QEmu/Layer2-nodejs/deps/node/out/Release/obj.target/mksnapshot.ia32/deps/v8/src/mksnapshot.o.d.raw
 -c -o /home/piranna/Dropbox/Proyectos/NodeOS/NodeOS-QEmu/Layer2-nodejs/deps/node/out/Release/obj.target/mksnapshot.ia32/deps/v8/src/mksnapshot.o
../deps/v8/src/mksnapshot.cc
/home/piranna/Dropbox/Proyectos/NodeOS/NodeOS-QEmu/Layer2-nodejs/deps/node/out/Release/obj.target/deps/openssl/libopenssl.a(eng_all.o):
En la función `ENGINE_load_builtin_engines':
eng_all.c:(.text.ENGINE_load_builtin_engines+0x46): referencia a
`ENGINE_load_padlock' sin definir
eng_all.c:(.text.ENGINE_load_builtin_engines+0x4b): referencia a
`ENGINE_load_gost' sin definir
collect2: error: ld returned 1 exit status
deps/openssl/openssl-cli.target.mk:193: recipe for target
'/home/piranna/Dropbox/Proyectos/NodeOS/NodeOS-QEmu/Layer2-nodejs/deps/node/out/Release/openssl-cli'
failed


Seems to be that OpenSSL command line executable is trying to find
this references. I have tried to disable the generation of that target
from GYP but seems more difficult to do that what I though. I know
OpenSSL has some issues with musl, but anyone knows how to fix this?
Seems OpenSSL support is required so NPM can work and to be able to
install packages... :-/

Otherwise, the Node.js static build is working flawlessly and the
problem with fstat() has been fixed with the cross-compiler :-D I'm
having some issues with compiled modules, but probably they are dues
to compile them outside the custom environment (with the current
Node.js version and glibc instead of the development one and musl),
I'll try to make it work from inside them :-)


-- 
"Si quieres viajar alrededor del mundo y ser invitado a hablar en un
monton de sitios diferentes, simplemente escribe un sistema operativo
Unix."
– Linus Tordvals, creador del sistema operativo Linux


      reply	other threads:[~2014-08-26 19:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-24 20:51 piranna
2014-08-24 21:05 ` Rich Felker
2014-08-24 21:23   ` piranna
2014-08-24 21:35     ` Luca Barbato
2014-08-25  9:18       ` piranna
2014-08-25  9:31         ` piranna
2014-08-25  9:49           ` Szabolcs Nagy
2014-08-25 15:48             ` Rich Felker
2014-08-26 19:05               ` piranna [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKfGGh2e5c5n5cnbgN4yuAimTqTATBWUqceGb1ih1=BHFwaiQQ@mail.gmail.com' \
    --to=piranna@gmail.com \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).