Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 31 Dec 2014 20:35:40 +0100
From: Szabolcs Nagy <>
Subject: Re: Failed to execute /init (error -2) for system-wide musl

* <> [2014-12-31 19:04:55 +0100]:
> On NodeOS we are having some problems creating an i686 cross-compiler
> using musl (
> 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
> with no lack. The fact is that

i think if static init works then try to use
that to boot up the system and then debug the
dynamic case..

you can run with a dynamic executable
as argument then you can debug the loader

if you have no debug tools on the target then
i think you can add dprintf's to early loader
code in src/ldso/dynlink.c which may help in
figuring out what fails

> 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, & As a shouldnt be needed

> curious side note, when installing the musl-linked gcc libraries, the
> /lib/ link dissapear from the cross-toochain folder,

sounds like a clfs buildsystem issue

i've seen the symlink disappearing on openwrt buildsystem once
(that one was not deterministic) i'm not sure what caused it

> 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
> :-/
> We are getting out of ideas, any clue about what could be happening?
> Greetings, and Happy New Year :-)

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.