From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: [PACKAGE] musl libc Date: Thu, 06 Oct 2016 21:08:01 +0000 Message-ID: <877f9lqj7y.fsf@we.make.ritual.n0.is> References: <87shun46de.fsf@elephly.net> <87vazihz8o.fsf@elephly.net> <87twf2hw0y.fsf@elephly.net> <87k2furtky.fsf@we.make.ritual.n0.is> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47709) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bsFue-0007ld-OJ for guix-devel@gnu.org; Thu, 06 Oct 2016 17:09:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bsFuZ-00013I-Jj for guix-devel@gnu.org; Thu, 06 Oct 2016 17:09:07 -0400 Received: from aibo.runbox.com ([91.220.196.211]:32798) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bsFuZ-00011z-Co for guix-devel@gnu.org; Thu, 06 Oct 2016 17:09:03 -0400 In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Vincent Legoll Cc: guix-devel Hi, Vincent Legoll 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