From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: [PACKAGE] musl libc Date: Sat, 06 Aug 2016 12:05:17 +0000 Message-ID: <87k2furtky.fsf@we.make.ritual.n0.is> References: <87shun46de.fsf@elephly.net> <87vazihz8o.fsf@elephly.net> <87twf2hw0y.fsf@elephly.net> 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]:57305) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bW0Lx-0004b3-Ku for guix-devel@gnu.org; Sat, 06 Aug 2016 08:05:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bW0Lv-0002wo-F8 for guix-devel@gnu.org; Sat, 06 Aug 2016 08:05:20 -0400 Received: from mithlond.libertad.in-berlin.de ([2001:67c:1400:2490::1]:36547 helo=beleriand.n0.is) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bW0Lv-0002wj-5D for guix-devel@gnu.org; Sat, 06 Aug 2016 08:05:19 -0400 In-Reply-To: <87twf2hw0y.fsf@elephly.net> 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: Ricardo Wurmus , Vincent Legoll Cc: guix-devel Ricardo Wurmus writes: > Vincent Legoll writes: > >> On Wed, Aug 3, 2016 at 1:24 PM, Ricardo Wurmus wrote: >>> I just built musl and found that it also installs “bin/musl-gcc”, a >>> wrapper of sorts, but it doesn’t work as it depends on a “gcc” >>> executable to be available. >> >> I did not see that as I probably had gcc installed in the profile with >> which i built musl... >> >>> Is this something that needs to work in order for this package to be >>> useful? >> >> Maybe not, but the default / documented way it is to be used is with >> the wrapper, so it is nice to have... >> >> Is this not the same with glibc, but in a more hidden way ? > > 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. > > ~~ Ricardo > > Is this package in a state where I can review sinit with it? It would be good if someone can comment on sinit too, as I commented on musl in general there too. -- ♥Ⓐ ng0 Current Keys: https://we.make.ritual.n0.is/ng0.txt For non-prism friendly talk find me on http://www.psyced.org