mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Justin Cormack <justin@specialbusservice.com>
To: musl@lists.openwall.com
Subject: Re: issues with headers?
Date: Thu, 13 Nov 2014 22:13:21 +0000	[thread overview]
Message-ID: <CAK4o1WwBJXgzTD1FkP5T8M_STLJhYsHiAmFsrw_4g7ny+CiC-w@mail.gmail.com> (raw)
In-Reply-To: <CAA7aPHgLC7BK7Z7GreGRqsMdg3485rnVN_nwzmXuvzqEv30qUA@mail.gmail.com>

On Thu, Nov 13, 2014 at 10:02 PM, stephen Turner
<stephen.n.turner@gmail.com> wrote:
> I have been trying various ways of compiling a musl system using gcc and
> found that GCC-4.7.3 does not seem to want to compile against musl headers.
> I install the linux headers in /usr/include then i install musl and move its
> headers to /usr/include. then i specify -I/usr/include to gcc and it errors
> every time (technically its /cross/usr/include as i have a separated env
> from my host system) The same compile works fine against musl libs but not
> the headers. The only change made from a working to a non-working system
> appears to be the use of the musl generated headers.
>
> In the scripts to build a musl toolchain (such as gregorr) the header
> location is not specified but sysroot is used (which obviously isn't linking
> against the headers)  I first started to see this issue when chroot'ing into
> a newly created musl gcc system.
>
> Is musl suitable as a stand alone libc replacement? Should i not be building
> against musl headers? If there is any reports or details you want me to
> provide please let me know.

You want to use a chroot or a VM with Musl if you are having these
issues. Sabotage or Alpine are good options. It will save a lot of
grief. Otherwise you are doing somethnig wrong that is hard to
diagnose without much moer info.

Justin


  reply	other threads:[~2014-11-13 22:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 22:02 stephen Turner
2014-11-13 22:13 ` Justin Cormack [this message]
2014-11-13 23:23   ` stephen Turner
2014-11-14 19:49     ` stephen Turner
2014-11-14 20:01       ` stephen Turner
2014-11-14 20:22         ` stephen Turner
2014-11-14 21:34           ` stephen Turner
2014-11-14 23:21             ` Szabolcs Nagy
2014-11-14 23:28               ` Matias A. Fonzo
2014-11-14 23:37           ` Matias A. Fonzo
2014-11-14 23:57             ` stephen Turner
2014-11-15  7:01       ` Weldon Goree
2014-11-17 23:54         ` stephen Turner

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=CAK4o1WwBJXgzTD1FkP5T8M_STLJhYsHiAmFsrw_4g7ny+CiC-w@mail.gmail.com \
    --to=justin@specialbusservice.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).