I suggest the following patch:
diff --git a/doc/guix.texi b/doc/guix.texi
index 972a6a776..3f148e390 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -2071,6 +2071,10 @@ ping -c 3 gnu.org
Setting up network access is almost always a requirement because the
image does not contain all the softwar
On Sun, Jan 27, 2019 at 10:45:58PM -0800, Chris Marusich wrote:
> Hi,
>
> What commit is this from? I just ran "make check" on
> 86228e569baaf1de0bfbb692fb2821df23f98b4a and although I do get one test
> failure, it looks very different from what you have shared.
>
> Some more questions to help t
Hi Gábor,
On Fri, 25 Jan 2019 09:11:04 +0100
Gábor Boskovits wrote:
> Hello,
>
> Ludo created the GSoC ideas page for this year:
> https://libreplanet.org/wiki/Group:Guix/GSoC-2019
>
> It is based on last year's page.
There is also the Outreachy May-August 2019 period:
https://www.outreachy.
Hi Ricardo,
On Mon, 28 Jan 2019 19:41:50 +0100
Ricardo Wurmus wrote:
> Did you run “make clean-go” before?
Nope. Did so now - the build of guix staging works now.
Thanks!
pgpaROXXhhog4.pgp
Description: OpenPGP digital signature
Dear,
I do not know if I am doing something wrong but I am not able to build
on x86_64:
guix build clang-runtime@3.5 -K
see error message below. Then I am going in
`/tmp/guix-build-clang-runtime-3.5.2.drv-0/build' and I try to inspect
as recommanded in "Debugging Build Failures".
I am not sure t
Danny Milosavljevic writes:
> Something more serious seems to be up with guix staging because I get,
> on trying "make" (after "./configure --localstatedir=/var") inside guix
> staging
> (commit df09e1d6e71f68a8fb44bcc9f13e625f9f9701a5) on x86_64:
>
> Backtrace:
> In ice-9/boot-9.scm:
>222
> On Jan 28, 2019, at 12:44 AM, Ricardo Wurmus wrote:
>
> Outputs are only generated when building the package.
>
> If all you need is the source code, however, you can use (package-source
> the-package) and use the resulting value as an input to another package.
Thanks Ricardo, I think this
Something more serious seems to be up with guix staging because I get,
on trying "make" (after "./configure --localstatedir=/var") inside guix staging
(commit df09e1d6e71f68a8fb44bcc9f13e625f9f9701a5) on x86_64:
Backtrace:
In ice-9/boot-9.scm:
222:29 19 (map1 _)
222:29 18 (map1 _)
222:29
Possible use-after free fix in mrustc commits:
https://github.com/thepowersgang/mrustc/commit/a51eea542ae086687ea2c4cb09321785f5cc6269
This was not in the mrustc 0.8.0 release yet.
pgp12KN34YAvz.pgp
Description: OpenPGP digital signature
Hi Ludo,
on second thought:
On Mon, 28 Jan 2019 15:39:33 +0100
Ludovic Courtès wrote:
> > /gnu/store/fw4yy7cgb5ahs9s2ir00bawnsl5zj7db-mrustc-0.8.0/bin/mrustc[...]
> munmap_chunk(): invalid pointer
Maybe the above causes
> src/tools/cargo/src/crates-io/lib.rs:65: BUG:src/expand/proc_macro.cpp:9
Hi Ludo,
> while reading from child process
^
Is that a real Pentium, or qemu on x86_64? We had some problems with
spawning child processes on the qemu transparent emulator.
pgphnzPYl3GKD.pgp
Description: OpenPGP digital signature
Hi,
Danny Milosavljevic skribis:
> On Mon, 28 Jan 2019 11:51:53 +0100
> Ludovic Courtès wrote:
[...]
>> Right. Initially linux.scm was for “kernel + Linux-specific packages”.
>> I think we should change it to have:
>>
>> • linux.scm for the kernel, header, ‘perf’, and little more.
>>
>>
Hello,
Rust fails to build on i686 on ‘staging’, so I don’t know if it’s
deterministic (the “unexpected EOF” reminds me of parallel build issues
with half-baked makefiles):
--8<---cut here---start->8---
BUILDING crates_io from crates-io v0.9.0 with features []
Ricardo Wurmus skrev: (28 januari 2019 13:03:42 CET)
>
>swedebugia writes:
>
>> Actually what is even nicer is emacs-debbugs and its ability to apply
>> patches from emails. The UI is somewhat lacking and I think we should
>> fork it so that it defaults to guix bugs and packages.
>
>FWIW you don’
Hello,
Ricardo Wurmus skribis:
> I tried to move most of the packages in gnu/packages/guile.scm to a new
> module gnu/packages/guile-xyz.scm.
>
> The only problem with this is that package-for-guile2.0 cannot be used
> in guile-xyz.scm. I cannot compile the module when there’s a reference
> to
Hi,
On Mon, 28 Jan 2019 11:51:53 +0100
Ludovic Courtès wrote:
> I support the idea; I’m not entirely sure about the core/ name space but
> that’s a secondary issue.
I support the idea, too.
> It may prove to be tricky though. For example, the set of dependencies
> of GCC has been steadily gro
swedebugia writes:
> Actually what is even nicer is emacs-debbugs and its ability to apply
> patches from emails. The UI is somewhat lacking and I think we should
> fork it so that it defaults to guix bugs and packages.
FWIW you don’t need emacs-debbugs to apply patches from emails, nor do
you
Ludovic Courtès writes:
>> I’d like to propose a reduction of the modules to a core set. To ensure
>> that they stay small we would move them to the directory
>> gnu/packages/core/. Adding new module references to any of the modules
>> in that directory would only be permitted for very good r
Hello,
Ricardo Wurmus skribis:
> for the past few days I’ve been trying to reduce the module closure of
> “coreutils” by inspecting the output of
>
> guix graph -t module coreutils
Much appreciated!
For the record, this is important for several reasons: it makes it
easier for (guix self) a
Hi,
Ricardo Wurmus skribis:
>> As an aside, should Icecat be on this list?
>
> This list is generated automatically. Icecat is a leaf package —
> nothing else depends on it.
It’s true that some leaf packages are “more important” than others, and
IceCat is one of them, but we usually check for
Hello Gábor,
Gábor Boskovits skribis:
> Ludo created the GSoC ideas page for this year:
> https://libreplanet.org/wiki/Group:Guix/GSoC-2019
>
> It is based on last year's page.
>
> I removed the Cuirass Web Interface project, as it was completed. We
> can discuss a project to improve it, but tha
Ivan Petkov writes:
> However, it appears that guix still insists on building the entire package
> even
> if we only depend on the "src" output. Is it possible to lazily build packages
> based on the type of dependency? Is this something the build system can
> finagle,
> or is this an inheren
22 matches
Mail list logo
