l...@gnu.org (Ludovic Courtès) skribis:
> Mark H Weaver skribis:
>
>> l...@gnu.org (Ludovic Courtès) writes:
>>> I’ve stopped the queue-runner while investigating. To be continued…
>>
>> For now, I would suggest downgrading the 'guix' on Hydra to be based on
>> guile-2.0 again, so that it can be
l...@gnu.org (Ludovic Courtès) skribis:
> I was able to reproduce it on hydra.gnu.org with:
>
> guix copy --to=hydra.gnunet.org
> /gnu/store/gi7r1v65zqhh8riqprq8nchfc9v9k156-guix-current
>
> which leads most of the time to SIGSEGV (I couldn’t get the SIGSEGV on
> my laptop):
Similar backtrace
On Sat, May 20, 2017 at 10:31:59PM +0200, Mathieu Othacehe wrote:
Hi Tomáš,
My question without answer is - how can I specify bootloader menu entries now?
You're right, you have to pass a now. The
documentation patch is still in review, you can find it here :
https://debbugs.gnu.org/cgi/bu
On Sat, May 20, 2017 at 10:31:59PM +0200, Mathieu Othacehe wrote:
>
> Hi Tomáš,
>
> > My question without answer is - how can I specify bootloader menu entries
> > now?
>
> You're right, you have to pass a now. The
> documentation patch is still in review, you can find it here :
>
> https://d
On Sat, May 20, 2017 at 10:52:34PM +0200, Danny Milosavljevic wrote:
Hi,
there's a doc patch in review by Mathieu (16 May 2017 15:03 +0200, "doc: Adapt to
multiple bootloader support", bug# 26339) in guix-patches.
As I have seen this feature on ML some time ago already, I didn't
expect to be
Hi,
there's a doc patch in review by Mathieu (16 May 2017 15:03 +0200, "doc: Adapt
to multiple bootloader support", bug# 26339) in guix-patches.
Although I wonder what menu-entries can be used for. What are you using it for?
Hi Tomáš,
> My question without answer is - how can I specify bootloader menu entries now?
You're right, you have to pass a now. The
documentation patch is still in review, you can find it here :
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26339#489
The example has been updated :
--8<-
Alex Sassmannshausen writes:
> Hello,
>
> This patch series goes back some time, but the need for it has not
> disappeared.
>
> It implements a general `wrap` phase that can be used in individual build
> systems to make sure binaries in those languages have access to all their
> propagated inputs
I'm running from GIT with HEAD on 12eecbf0bb798f99454a46c191bb0ec6bdef1aa5.
It seems that menu-entry is still described in documentation
doc/guix.texi:15337
but code seems to abandon the use already in favor of boot-parameters
at least to my level of understanding.
My question without answer i
Mark H Weaver skribis:
> l...@gnu.org (Ludovic Courtès) writes:
>> I’ve stopped the queue-runner while investigating. To be continued…
>
> For now, I would suggest downgrading the 'guix' on Hydra to be based on
> guile-2.0 again, so that it can be building things while we sort this
> out. What
l...@gnu.org (Ludovic Courtès) writes:
> I’ve stopped the queue-runner while investigating. To be continued…
For now, I would suggest downgrading the 'guix' on Hydra to be based on
guile-2.0 again, so that it can be building things while we sort this
out. What do you think?
Mark
Pjotr Prins skribis:
> On latest guix d30ce4a7e2ba8f4eca7b99bb8483353c753e91bf
>
> ./pre-inst-env guix pack hello
>
> works. But this does not:
>
> ./pre-inst-env guix pack hello -f docker
>
> I am sure guile-json is in the path (see below).
>
> The following derivation will be built:
>
On latest guix d30ce4a7e2ba8f4eca7b99bb8483353c753e91bf
./pre-inst-env guix pack hello
works. But this does not:
./pre-inst-env guix pack hello -f docker
I am sure guile-json is in the path (see below).
The following derivation will be built:
/gnu/store/xhfrvmh7vh2ipm32rdyisagnr5ac46
* guix/build/python-build-system.scm (wrap): Use
'wrap-language-program'.
---
guix/build/python-build-system.scm | 36
1 file changed, 8 insertions(+), 28 deletions(-)
diff --git a/guix/build/python-build-system.scm
b/guix/build/python-build-system.scm
inde
* guix/build/perl-build-system.scm (wrap): New procedure.
(%standard-phases): Add 'wrap' phase.
---
guix/build/perl-build-system.scm | 15 +--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/guix/build/perl-build-system.scm b/guix/build/perl-build-system.scm
index b202
* guix/build/utils.scm (program-wrapper): New procedure.
---
guix/build/utils.scm | 36
1 file changed, 36 insertions(+)
diff --git a/guix/build/utils.scm b/guix/build/utils.scm
index e8efb0653..af5583651 100644
--- a/guix/build/utils.scm
+++ b/guix/build/util
Hello,
This patch series goes back some time, but the need for it has not
disappeared.
It implements a general `wrap` phase that can be used in individual build
systems to make sure binaries in those languages have access to all their
propagated inputs at runtime, by setting an appropriate enviro
17 matches
Mail list logo
