From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: musl troubleshooting faq
Date: Wed, 30 May 2012 20:44:54 -0400 [thread overview]
Message-ID: <20120531004454.GM163@brightrain.aerifal.cx> (raw)
Hi all,
I was thinking a bit about the typical problems people have run into
trying to get started using musl, and possibly updating the
documentation or adding a troubleshooting faq to address them. Here
are some that came to my mind:
- Distro-patched GCC with stack protector on by default
- Lack of -Bsymbolic-functions support in old binutils
- Trying to use wrong libraries (glibc-linked host libraries)
- GCC wrapper not working with (already-wrapped) Aboriginal toolchain
- Need to remove GCC include files from include path
- Feature test macros for building software
Any other issues come to mind? (Or ideas how to make these issues
simpler for new users?)
Rich
reply other threads:[~2012-05-31 0:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120531004454.GM163@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--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).