<Apteryx>efraim: gcc build failed with segfault. I guess it ran out of memory. manpages seems to still suffer from the same problem (gcc.1 has for only text "timestamp" in it). Hmm.
<Apteryx>I'm confused... After a failed build with 'guix build --keep-failed', I see in the derivation tree: "build/ environment-variables gcc-5.4.0/". Where are the built artefact? There appear to be both under build/ and gcc-5.4.0/.
<Apteryx>looks like some phase from our build system is corrupting the manual page source file.
<kmicu>Writing Nix is terrible experience b/c Nix DSL has 0 tools. Guix by embedding DSL in Guile has plenty of them. That’s the one reason. There is more but I cannot find civodul’s mails about the topic at the moment.
<kmicu>ACTION should also add a poor joke “What you’re referring to as Nix lang, is in fact, Nix/Bash, or as I’ve recently taken to calling it, Nix plus ton of Bash.”.
<Apteryx>civodul: thanks for looking at some of my patches!
<Apteryx>I will prepare an update for the texi manual with an example using the android-udev-rules package.
<Apteryx>Also, I'm trying to test a new patch for building the man pages of gcc, but when I run it with ./pre-inst-env guix build -K -c 1 email@example.com, it goes on to rebuild all the guix dependencies (it's a world rebuild inducing change). Anyway to take guix out of the loop? Building gcc itself is long enough as it stands.
<Apteryx>Maybe I could use my non-dev guix (from guix pull), and combine the "--file" and "--expression" flags of its build subcommand to tell it to use firstname.lastname@example.org from ~/src/guix/gnu/packages/gcc.scm ?
<civodul>Apteryx: that's because everything depends on gcc@5, and gcc@5 is defined as (package (inherit gcc-4.7) ...)
<civodul>for testing purposes, you could define a GCC variant that inherits from gcc@5