Re: Bug on fstat()?

[Rich Felker <dalias@libc.org>]

On Mon, Aug 25, 2014 at 11:49:03AM +0200, Szabolcs Nagy wrote:
> * piranna@gmail.com <piranna@gmail.com> [2014-08-25 11:31:28 +0200]:
> > > So, is g++ mandatory for compilation? Is there any solution? I'll try
> > > to set CXX to musl-gcc too, but didn't see anything about this and I'm
> > > not sure if it would work... If it doesn't work, would I need to
> > > create a musl-g++ wrapper?
> > 
> > Confirmed: doesn't work, it has failed just in the first C++ source
> > code file it has found:
> > 
> 
> musl-gcc is just a thin gcc wrapper (uses a custom spec file
> to locate the standard headers and other libc files)
> 
> eg. it does not have a libstdc++ linked against musl so it
> cannot build c++ code

In principle it should be possible to make it work. libstdc++.so
actually works fine with musl due to the ABI-compat; the problem is
the nasty precompiled header files that have already pulled in junk
from glibc's headers. If there's a way around that, it may be possible
to get musl-gcc working with C++. Nobody has tried it yet as far as I
know, though.

> use a musl cross compiler for your target with c++ support
> (eg http://musl.codu.org/ has prebuilt ones but you can build
> musl-cross yourself) or build on a musl based system (sabotage
> or alpinelinux, they probably already have node.js packaged)

Yes, this is the best option. You might need to tweak their builds to
get a static binary though.

Rich