<ng0>I'll post my ghc 8.0.1 progress today on our list. I think someone else with a selfinterest in using ghc should work on this. maybe someone who originally pacakged it for guix or fixed the old ncurses problem before. just to know, there's an additional problem with ncurses added on top of that now.
<brendyn>Right. I'm trying to build a complete end user friendly distro out of Guix. So I think "ok, so people should be able to change keyboard layouts, right? basic feature" GDM? nope. SDDM? Sorta. In theory it can load xkb layouts
<quigonjinn>In my arm-none-eabi module, there is a non-puclic package that builds gcc --without-headers. The newlib package builds with this bootstrap gcc. And then gcc is built again on top of newlib. Is my approach compiant with guix, or am I missing something?
<civodul>so you can do: ./pre-inst-env guix build -e '(begin (use-modules(gnu packages cross-base)) (cross-gcc "arm-none-eabi"))' -n
<civodul>but you first need to add a case for "arm-eabi" in 'glibc-dynamic-linker'
<brendyn>So these seem like two different versions of the same font, but under different licenses. is CC BY ND ok?
<quigonjinn>civodul: I did add a case in 'glibc-dynamic-linker'. Bare cross-gcc builds, as does newlib on top of it. Cross-gcc(final) with newlib support builds on top of newlib. I am unsure if this bare cross-gcc is needed. With my current knowledge i conclude it is.
<civodul>quigonjinn: if that doesn't work for you, i'd suggest emailing help-guix for further debugging
<rsriniva>hello! just finished a from scratch install of guix sd 0.11 on my desktop machine and have a couple of questions
<ng0>motivating comments by other packagers on 0ad: \\# rebuild premake again... this is the most stupid build system
<ng0>question: if something is proven to work with libressl, can't we just defualt to building that application with libressl instead? for opensmtpd i did it because it is upstream dependency. for gloox i know it must work with libressl as drop in replacement for openssl.
<civodul>ng0: i think we should be consistent, so for now that would mean using OpenSSL
<ng0>why when we are flexible with the model guix offers? building opensmtpd with libressl makes sense. rebuilding everything with libressl and patching the failing packages will be a long work. we can move slowly towards this while we are still at 40k packages.
<kyamashita>It does! Let's see if it can support SSL using OpenSSL...
<kyamashita>Even worse luck... lynx doesn't even see OpenSSL.
<ng0>there is a more or less big amount of work involved in libressl compability, i don't know how much distros upstream, so maybe we have to repeat the cycle others did already. some applications justwork, some need to be patched. I will add a note for myself and write to the mailinglist, civodul.
<ng0>gloox or what it was called failed in a funny way for one gnutls test with both libressl and openssl builds. I suppose it will work as tests succeeded, but we'll only know when complains get in in the form of bugreports :)
<ng0>well, openssl enabled build had 1 more failure than libressl. i think those are outputs i can ignore.. maybe some test which wanted to phone a random server