<guix-vits>ArneBab_: did you're tried to pass --no-auto-compile to guile 2.2, as a workaround?
<ArneBab_>guix-vits: no — can I do that when installing from Guix?
<ArneBab_>guix-vits: it’s not that my programs don’t run: they just show lots of errors when I start them
<ArneBab_>guix-vits: but thank you for your answer!
<abralek>Hi, I amend a set of my patches and sent v2 to the bug-track. And now I see that my patches are failing here https://patchwork.cbaines.net, but It seems to me that it doesn't apply them as a set anymore.
<abralek>Could someone explain me how it should be done properly?
<jboy>I find the manual a little confusing since it suggests that `./pre-inst-env` and `etc/indent-code.el` are already present when you checkout the repository, but you actually have to run configure/make first
<jstierhof>Hello everyone, stupid question regarding package definition. I try to build software which requires libx11 and the Intrinsics.h from libxt, however, they are not found by default and I can only specify --x-includes for one directory. Does anyone know how to deal with that? Thanks!
<dongcarl>Anyone know why `gcc -v` has the "Configured with:" line blanked out?
<rekado_>dongcarl: to prevent /gnu/store references from being retained.
<rekado_>having the references appear in text would let the reference checker record them and increase the GCC package closure.
<rekado_>we sometimes need to erase references like that to keep the closure size smaller. We did this in Icecat and in Perl.
<rekado_>in both cases they recorded the environment in which they were configured which led to all sorts of items to be retained as part of the package closure even though they were not needed at runtime.
<nckx>jstierhof: Tricky. If the sources use ‘#include <…>’ you can try adding multipile -I…s to CFLAGS. That should work. Other options are patching the source or (probably worse) creating a little union include/ directory in .
<nckx>guix-vits: No, that patch changes run-time behaviour of libXt, not where it installs headers. jstierhof problem is that the package expects all ‘X’ headers to be under 1 directory, which can't be fixed by a patch. A union package, yes, but that's probably overkill at this time.
<guix-vits>nckx: about "... /msg ... without a leading space?" also i have a strange thing in *shell* when using `guile` inside of emacs: it refuses to evaluate a code that contains copied newline (M-w, C-y).
<leoprikler>If I were to add a package that is a perl script (specifically convmv), should I name it $package or perl-$package?
<nckx>leoprikler: If it's mainly used at the command line, no perl-. If mainly a library, perl-.
<leoprikler>and if it's the former, I also don't add it to perl.scm but rather somewhere else, right?
<nckx>E.g. ‘rename’ is written entirely in Perl but that's just an implementation detail, everybody wants the command.
<vagrantc>i've got it running ... wondering if the recent changes to guile-next allow guix pull to work again