From: "piranna@gmail.com" <piranna@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Bug on fstat()?
Date: Sun, 24 Aug 2014 23:23:27 +0200 [thread overview]
Message-ID: <CAKfGGh0KVqrYDgQkd87AHBA0+x7Hx0rWrRmiFKh-P-xranguDA@mail.gmail.com> (raw)
In-Reply-To: <20140824210539.GT12888@brightrain.aerifal.cx>
> What prefix is musl-gcc installed in?
I'm using the musl packages availables on Ubuntu Unicorn, musl-gcc is
available at /usr/bin/musl-gcc and musl includes are at
/usr/include/i386-linux-musl
> And have you done anything to modify it or added additional include paths for it? The above symlinks don't make sense for a typical out-of-the-box installation.
I've not modified musl source code, only modifications have been to
add that symlinks for linux, asm & asm-generic includes so they are
available to Node.js during compilation. I didn't found a cleaner way
to do it. They are not required by Node.js itself, but instead by
libuv.
> I suspect you've somehow gotten -I/usr/include added to the CFLAGS during build
> (either doing it yourself, or as a result of a broken build script) if
> adding symlinks to /usr/include made a difference, in which case you
> may be using glibc's headers, not musl's, and thus getting broken
> results.
The build scripts are generated by GYP and the Node.js build process,
that I'm generating with
CC=musl-gcc ./configure --fully-static --without-ssl
(--fully-static is a flag that I've patched that adds '-static' to gcc call)
/usr/include should not be referenced, if so, I wouldn't need to add
the symlinks for /usr/include/linux and /usr/include/asm-generic :-/
Anyway, I'll review the full build process.
--
"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 prev parent reply other threads:[~2014-08-24 21:23 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 [this message]
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
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=CAKfGGh0KVqrYDgQkd87AHBA0+x7Hx0rWrRmiFKh-P-xranguDA@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).