From: "piranna@gmail.com" <piranna@gmail.com>
To: musl@lists.openwall.com
Subject: Failed to execute /init (error -2) for system-wide musl libc
Date: Wed, 31 Dec 2014 19:04:55 +0100 [thread overview]
Message-ID: <CAKfGGh1TmtdCuoSaxm9wv72e5ry0yCDM_zsNvrfLKH9YP_eRpw@mail.gmail.com> (raw)
On NodeOS we are having some problems creating an i686 cross-compiler
using musl (https://github.com/NodeOS/NodeOS/pull/89).
The point is that by generating a fully statically linked Node.js
executable it boot correctly, but by using a dynamically one we get a
"Failed to execute /init (error -2)" error. We have crafted the
cross-compiler following the instructions at
http://clfs.org/view/clfs-embedded with no lack. The fact is that
executables compiled with the cross-toolchain works on our desktops
but they don't on QEmu, and we've added all the dynamic libraries that
readelf request (only libc.so, libstdc++.so & libgcc_s.so). As a
curious side note, when installing the musl-linked gcc libraries, the
/lib/ld-musl-i386.so.1 link dissapear from the cross-toochain folder,
but also adding it by hand all the dynamic linked executables refuse
to load on QEmu, also a simple "Hello World" that only depends on
libc.so :-/
We are getting out of ideas, any clue about what could be happening?
Greetings, and Happy New Year :-)
Jesús Leganés Combarro "piranna"
--
"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
next reply other threads:[~2014-12-31 18:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 18:04 piranna [this message]
2014-12-31 19:35 ` Szabolcs Nagy
2014-12-31 19:49 ` piranna
2014-12-31 20:08 ` Matias A. Fonzo
[not found] ` <CAKfGGh0EoXAb7FH2pn2FW1ND7Bts8XSjj2ur-aoc6Ugbb6atNw@mail.gmail.com>
2014-12-31 21:09 ` Matias A. Fonzo
2014-12-31 21:25 ` piranna
2014-12-31 19:40 ` Isaac Dunham
2014-12-31 20:17 ` piranna
2014-12-31 20:36 ` piranna
2014-12-31 21:55 ` Isaac Dunham
2015-01-01 20:02 ` piranna
2015-01-03 23:37 ` Andy Lutomirski
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=CAKfGGh1TmtdCuoSaxm9wv72e5ry0yCDM_zsNvrfLKH9YP_eRpw@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).