all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <ngillmann@runbox.com>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PACKAGE] musl libc
Date: Thu, 06 Oct 2016 21:08:01 +0000	[thread overview]
Message-ID: <877f9lqj7y.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <CAEwRq=rASV+nEZ=jmdr5UfH443C5DH50+H9aFN167=EVUSPatA@mail.gmail.com>

Hi,

Vincent Legoll <vincent.legoll@gmail.com> writes:

>>> We usually don’t use the “gcc” package directly in Guix.  Instead we use
>>> “gcc-toolchain”, which also comes with a wrapper around the linker that
>>> ensures that binaries are linked with libraries in the store, ensuring
>>> that things generally just work™.
>>>
>>> I think more work would be needed to ensure that packages can actually
>>> successfully be linked with musl, but I’m not at all familiar with this.
>>> I had mixed success with a GCC ARM cross-compiler toolchain linking with
>>> newlib, so I know that it’s not exactly obvious how to do this right,
>>> but I find it hard to understand this.
>>>
>>> Have you tried building something that links with the libc provided by
>>> this musl package instead of the GNU libc?  I’m not opposed to adding
>>> the package, but I’d like it to be usable.
>
> I'm not sure...
>
> I built musl, made the sinit package use the musl-wrapper as CC,
> and it worked (it builds => it works) but couldn't test that sinit as
> replacement for pid 1...

I was wondering what happened to musl? Are there any problems left,
anything the people you have been working with can help you to solve? I
had the impression it was almost ready.

> -- 
> Vincent Legoll

  reply	other threads:[~2016-10-06 21:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-30 12:19 [PACKAGE] musl libc Vincent Legoll
2016-08-02  8:45 ` ng0
2016-08-02 14:01 ` Ricardo Wurmus
2016-08-02 20:18   ` Vincent Legoll
2016-08-03 11:24     ` Ricardo Wurmus
2016-08-03 11:38       ` Vincent Legoll
2016-08-03 12:35         ` Ricardo Wurmus
2016-08-06 12:05           ` ng0
2016-08-08 13:26             ` Vincent Legoll
2016-10-06 21:08               ` ng0 [this message]
2016-10-08 12:38                 ` David Craven
2016-10-08 13:54                   ` ng0
2016-10-08 14:53                     ` David Craven
2016-10-08 15:12                       ` ng0
  -- strict thread matches above, loose matches on Subject: below --
2016-08-03 13:25 David Craven
2016-08-12 19:15 ` Ricardo Wurmus
2016-08-13  9:32   ` Ricardo Wurmus
2016-08-13  9:44     ` Vincent Legoll
2016-08-13  9:55       ` David Craven
2016-08-13 10:00         ` Vincent Legoll
2016-08-13 10:17           ` David Craven
2016-08-14  7:46             ` Ricardo Wurmus
2016-08-08 16:47 David Craven
2016-08-08 18:43 ` Vincent Legoll
2016-08-08 18:46   ` David Craven

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=877f9lqj7y.fsf@we.make.ritual.n0.is \
    --to=ngillmann@runbox.com \
    --cc=guix-devel@gnu.org \
    --cc=vincent.legoll@gmail.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.