Re: Packaging Coq

I haven’t done the obvious thing… The package in Nixpkgs does more things, so I’ll try to change my recipe accordingly. pgp4000r6YKBh.pgp Description: PGP signature

Re: Packaging Coq

Since people are commenting only on the recipe, I guess I need to clarify that I’d like to know why it fails to build. pgpVm4hxBpXvG.pgp Description: PGP signature

Re: Packaging Coq

> Should these arguments not be a double -- ?? No. pgpIWWS3Y1b3c.pgp Description: PGP signature

Packaging Coq

Does anyone know how to proceed? ;;; GNU Guix --- Functional package management for GNU ;;; Copyright © 2014 Nikita Karetnikov ;;; ;;; This file is part of GNU Guix. ;;; ;;; GNU Guix is free software; you can redistribute it and/or modify it ;;; under the terms of the GNU General Public License

Re: On-line hackathon on Sep. 27-28?

> How could a non programmer help? How would you like to help? For instance, would you like to learn how to program? In any case, the good first step is to install Guix and play around. Look at the command line tools, read the documentation. Have a problem? Ask on the #guix channel on Freenode,

Re: pypi->guix script

> For more details and source code, check out the git repository: > https://gitorious.org/davexunit/pypi2guix Why not add it to Guix? pgp5DxVq5VsRV.pgp Description: PGP signature

Re: Proposal: prefetch tarballs in a batch

> BTW, I’ve been traveling lately, and I’ve really missed ‘guix > prefetch’. Heh, that was the motivation. > So if you have spare time to pour into it, or if someone else wants to > take it over, that’d be nice! I doubt so, unfortunately. So please do take it over if you can. pgpMOhIZmPKkm.pg

Re: [PATCH] gnu: hurd: Add Hurd Minimal.

> ++if test "x$cross_compiling" = "xyes"; then > ++ # It may be that we don't have a working libc yet, for instance > ++ # because we're bootstrapping the cross-compilation tool chain. > ++ # Thus, use this undocumented Autoconf macro designed for this. > ++ AC_NO_EXECUTABLES > ++ echo do

Re: [PATCH] Add mcrypt

> This patch adds Mcrypt, and two library dependencies. Comments > welcome. I believe the libraries should be listed in the commit message as new variables. Ludo, WDYT? > + (method url-fetch) > + > + (uri (string-append "mirror://sourceforge/mcrypt/mcrypt-" Extraneous newline. > +

Re: Proposal: prefetch tarballs in a batch

>>> Does the installation seem sane, basically? Do ‘guix build’, ‘guix >>> package’ etc. work somehow, or not even? >> Turns out I can’t even build ‘hello’ > Please say exactly why you “can’t”. Currently, it fails due to the “bad file descriptor” error. > Why the hell do you keep deleting the

Re: URL wrong for nix upstream

> Funny, I've never had this issue. I’ve had, but couldn’t reproduce it reliably. pgpH7nnvD3SYj.pgp Description: PGP signature

Re: torify w3m: ERROR: ld.so: object ‘libtorsocks.so’ cannot be preloaded

> I'm reasonably sure it means that w3m is not getting torified at all. What about the TorCheck response: “Congratulations. This browser is configured to use Tor.”? pgpNp0hGnblkf.pgp Description: PGP signature

torify w3m: ERROR: ld.so: object ‘libtorsocks.so’ cannot be preloaded

‘torify w3m https://check.torproject.org’ returns the following error message before showing “Congratulations. This browser is configured to use Tor.” Is it harmless? ERROR: ld.so: object '/gnu/store/2g7lx2qz06vlb241gfr6bpyp6mc5a24z-torsocks-1.2/lib/torsocks/libtorsocks.so' from LD_PRELOAD cann

Re: Proposal: prefetch tarballs in a batch

dex 000..dbcef0f --- /dev/null +++ b/guix/scripts/prefetch.scm @@ -0,0 +1,141 @@ +;;; GNU Guix --- Functional package management for GNU +;;; Copyright © 2014 Nikita Karetnikov +;;; Copyright © 2014 Ludovic Courtès +;;; +;;; This file is part of GNU Guix. +;;; +;;; GNU Guix is free software; you ca

Re: ‘package-derivation’ fails with “No such file or directory”

> Yes, probably /var/guix/db/db.sqlite (or similar) was left behind, > leading to an inconsistency (this database contains info about what’s in > the store.) Indeed, thanks. pgpbFMwu3FcZ1.pgp Description: PGP signature

‘package-derivation’ fails with “No such file or directory”

I’d like to test a patch with the empty store. I deleted ‘/gnu’ and reinstalled Guix. But whenever I call (package-derivation store hello), I run into “ERROR: In procedure open-file: No such file or directory: "/gnu/store/…-guile-bootstrap-2.0.drv".” Did I forget to delete any cached files? pg

Re: GnuTLS: Upgrade to 3.3.1 (fails)

>> make[4]: Entering directory >> '/tmp/nix-build-gnutls-3.3.1.drv-0/gnutls-3.3.1/tests/cert-tests' >> PASS: pathlen >> PASS: aki >> FAIL: pem-decoding >> SKIP: template-test >> make[5]: Entering directory >> '/tmp/nix-build-gnutls-3.3.1.drv-0/gnutls-3.3.1/tests/cert-tests' > Does test-suite.log

Re: GnuTLS: Upgrade to 3.3.1 (fails)

>> make[4]: Entering directory >> '/tmp/nix-build-gnutls-3.3.1.drv-0/gnutls-3.3.1/tests/cert-tests' >> PASS: pathlen >> PASS: aki >> FAIL: pem-decoding >> SKIP: template-test >> make[5]: Entering directory >> '/tmp/nix-build-gnutls-3.3.1.drv-0/gnutls-3.3.1/tests/cert-tests' > Does test-suite.log

Re: Proposal: prefetch tarballs in a batch

What options would you like to see implemented? diff --git a/guix/scripts/prefetch.scm b/guix/scripts/prefetch.scm new file mode 100644 index 000..16346bb --- /dev/null +++ b/guix/scripts/prefetch.scm @@ -0,0 +1,149 @@ +;;; GNU Guix --- Functional package management for GNU +;;; Cop

Re: GSoC status

> FWIW, I received that message (dated Wed, 09 Apr 2014 21:28:54 +0200), > as I was on the CC list. In fact, I received two copies of it. > I see that it was also sent to Thomas Schwinge, Samuel Thibault, Richard > Braun, Andreas Enge, and Nikita Karetnikov. It would be interesti

GnuTLS: Upgrade to 3.3.1 (fails)

‘gnutls-remove-gnutls_secure_malloc.patch’ fixes the following issue: make[4]: Entering directory '/tmp/nix-build-gnutls-3.3.1.drv-0/gnutls-3.3.1/guile/src' CC guile_gnutls_v_2_la-core.lo core.c: In function 'scm_init_gnutls': core.c:3369:3: error: 'gnutls_secure_malloc' undeclared (first

Re: Proposal: prefetch tarballs in a batch

>> 1. Should the recursion stop when ‘fixed-output-derivation?’ returns #t? > I think so. In general fixed-output derivations are the things you > would like to pre-fetch; so you would typically call ‘build-derivations’ > on these to do the actual pre-fetching. Could you show a package with a fi

[PATCH] openssh: Add another mirror.

The original mirror doesn’t respond. Please verify and push. From cbac7ff6ef8f7c02d01331b77511ba8c9dadc45d Mon Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Sat, 12 Apr 2014 16:18:45 +0400 Subject: [PATCH] openssh: Add another mirror. * gnu/packages/ssh.scm (openssh): Add the mirror

Re: Proposal: prefetch tarballs in a batch

So, in order to add a tarball to the store, one can write: $ ./pre-inst-env guile scheme@(guile-user)> ,use (guix store) (guix packages) (guix derivations) (gnu packages wget) scheme@(guile-user)> (define s (open-connection)) scheme@(guile-user)> (package-source-derivation s (package-source wget)

Re: [PATCH] gnu: Python: disable failing tests on MIPS64.

> What does 'python -c "import platform; print(platform.machine())"' > return on your machine ? ‘mips64’. > The tests that fail are now disabled on mips64. I ran ‘make clean’ & co., rebuilt Python; and the tests succeeded. pgpZyyuH117PD.pgp Description: PGP signature

Re: [PATCH] gnu: Python: disable failing tests on MIPS64.

> I've tested this on the Loongson 3A machine, and it works as expected. Python fails for me on Lemote YeeLoong. $ git rev-parse HEAD 32d5c729522d02fe973cb245fe26262f040e0c13 == FAIL: test_issue_8959_a (ctypes.test.test_callback

Re: [PATCH 2/3] gnu: Add man-db

> For some reason I'm having trouble pushing to the git repo. What kind of trouble? pgpH8KflVVdZ4.pgp Description: PGP signature

Re: Proposal: prefetch tarballs in a batch

>> Is there a function that accepts a package name and returns a list of >> implicit inputs? > No, because by definition, those “implicit inputs” are not listed in the > package object. Instead, they are added by the build system (see > build-system/gnu.scm.) > That’s why I suggested using deriv

Re: Proposal: prefetch tarballs in a batch

> The simplest way to do it would be by walking the package DAG: start > from ‘foo’, accumulate its ‘package-source’, then traverse its inputs, > etc. Recursion would stop at the implicit inputs (GCC, glibc, > Coreutils, etc.), though. > If you’d like implicit inputs to be taken into account, the

Proposal: prefetch tarballs in a batch

By default, Guix fetches source tarballs on demand. You download a tarball, configure and install, move to the next one, and so on. But it may be useful to fetch all the prerequisites before building. For instance, you travel frequently and don’t usually have Internet access. So it’d be nice to

Re: wip-signed-archives progress report

> Nikita: comments welcome on the two commits I just pushed in > wip-signed-archives. Thanks for working on it. One question: in the past, you told me to avoid ‘false-if-exception’. If it’s an issue here, can we replace it with something else? pgpNylqhDAzdE.pgp Description: PGP signature

Re: master: FAIL: tests/store.scm

>> FAIL: tests/store.scm >> FAIL: tests/guix-build.sh >> FAIL: tests/guix-register.sh > These two failures are because the ‘test-tmp’ directory predates the > nix → guix change in commit f5768afa333bbc8167ef2e33db44c9bb64bef0be. > An annoyance, but that should be fixed by either “rm -rf test-tmp

Re: master: FAIL: tests/store.scm

>> Which log files would you like to see? > The SRFI-64 $top_builddir/*.log files, and $top_builddir/test-suite.log. $ git rev-parse HEAD 6f58d582432fe46c163f61ddf8f653584f4f7be8 FAIL: tests/store.scm FAIL: tests/guix-build.sh FAIL: tests/guix-register.sh Starting test store Group begin: s

Re: [PATCH 2/2] guix substitute-binary: Support the Signature field of a narinfo file.

>>> I was about to say you could push to master, but since the new >>> substitute-binary will refuse any unsigned archives[*], it may be wiser >>> to push to a special branch so we can test it in real life before >>> merging into master. >> Should the special branch be based on ‘master’ or ‘core-u

Re: [PATCH 2/2] guix substitute-binary: Support the Signature field of a narinfo file.

> I was about to say you could push to master, but since the new > substitute-binary will refuse any unsigned archives[*], it may be wiser > to push to a special branch so we can test it in real life before > merging into master. Should the special branch be based on ‘master’ or ‘core-updates’?

[PATCH 2/2] guix substitute-binary: Support the Signature field of a narinfo file. (was: Signed archives (preliminary patch))

on Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Wed, 12 Mar 2014 21:21:39 + Subject: [PATCH 1/2] nar: Clarify that 'assert-valid-signature' accepts a string. * guix/nar.scm (assert-valid-signature): Turn a comment into a docstring and improve the wording. --- guix/nar.scm

Re: Signed archives (preliminary patch)

>> Actually, the problem with making ‘assert-valid-signature’ public is >> that it raises &nar error conditions. I’ve looked through the code; now I need even more information. Please elaborate. >> It could be changed to raise a more generic &signature-error, but then >> ‘restore-file-set’ would

Re: Signed archives (preliminary patch)

>> I think the current docstring of ‘assert-valid-signature’ is not correct >> since ‘signature’ must be a string (as produced by >> ‘canonical-sexp->string’), not an sexp. > In guix/nar.scm, the comment is: > (define (assert-valid-signature signature hash file) > ;; Bail out if SIGNATURE,

Re: master: FAIL: tests/store.scm

Apologies for the sloppy reporting. Let me explain why it’s the case. I ran ‘make check’ multiple times. These tests failed when I cloned the repo and ran ‘make check’ for the first time: tests/derivations.scm, tests/store.scm, tests/guix-build.sh, tests/guix-register.sh. These ones failed when

Re: Signed archives (preliminary patch)

> + ((nar-invalid-hash-error? condition)) Should be ((nar-invalid-hash-error? condition) #t), I guess. Otherwise, the procedure returns ‘undefined’. pgpgUXbCKRGuS.pgp Description: PGP signature

Re: Signed archives (preliminary patch)

.scm @@ -0,0 +1,212 @@ +;; -*- mode: scheme; coding: utf-8 -*- +;; +;; This module was renamed from (weinholt text base64 (1 0 20100612)) to +;; (guix base64) by Nikita Karetnikov on +;; February 12, 2014. +;; +;; Copyright © 2009, 2010 Göran Weinholt +;; +;; This program is free software: you can red

Re: Want help with writing package recipe

> I used guix hash -f base32 to export the base32 hash, which is: > i5q225g6twsg5egicgpt6ub7hn4m7pdzg56hwxx57jm4o4ns5fgq You need ‘nix-base32’, which is the default format, so use ‘guix hash’. > I've written a recipe for gtypist located here: > http://pastebin.com/ysLHJUWg Please include

Re: core-updates: FAIL: tests/builders.scm; tests/packages.scm; tests/store.scm

> Could you send test-suite.log and tests/{builders,packages,store}.log? > (Note: tests/foo.log is different from foo.log!) I can reproduce only the ‘tests/store’ failure on 1faca892a35941b6eed2d6c04478f9f77ab81e15. accepted connection from pid 1942, uid 1000 ;;; note: auto-compilation is enabled

master: FAIL: tests/store.scm (was: master: the tests take ages)

> Yes, some of the tests involve downloading a couple of packages, and > building them. This takes a while the first time you run ‘make check’, > but is fast in subsequent runs (unless you removed ‘test-tmp’.) Now ‘tests/store’ fails on ece262461625e80957d904f39a6818286099d367. =

master: the tests take ages

On master, ‘make check’ hangs after PASS: tests/base32.scm PASS: tests/hash.scm PASS: tests/pk-crypto.scm PASS: tests/pki.scm Any clues? pgpIlOqNfFHML.pgp Description: PGP signature

core-updates: coreutils: FAIL: tests/misc/nohup

Cyril reported this on IRC. Indeed, one of the tests fails (I tested on i686). Is there a need to report upstream? GNU coreutils 8.22: ./tests/test-suite.log # TOTAL: 551 # PASS: 412 # SKIP: 1

Re: Signed archives (preliminary patch)

+;; This module was renamed from (weinholt text base64 (1 0 20100612)) to +;; (guix base64) by Nikita Karetnikov on +;; February 12, 2014. +;; +;; Copyright © 2009, 2010 Göran Weinholt +;; +;; This program is free software: you can redistribute it and/or modify +;; it under the terms of the GN

Re: Signed archives (preliminary patch)

> There’s an important check missing here: the code verifies that BODY* is > a valid signature, but it doesn’t check whether what it signs > corresponds to this narinfo up to but excluding the ‘Signature’ field. Oh, indeed. > 5. pass the hash to the signature verification procedure. Then, it s

Re: Signed archives (preliminary patch)

> How do you envision the transition from this single-signature > architecture to one where other users and/or independent build farms > can add their signatures to hydra? Will those signatures be treated > differently than the signatures created by hydra.gnu.org? Will they > be stored and sent t

Re: Signed archives (preliminary patch)

-*- +;; +;; This module was renamed from (weinholt text base64 (1 0 20100612)) to +;; (guix base64) by Nikita Karetnikov on +;; February 12, 2014. +;; +;; Copyright © 2009, 2010 Göran Weinholt +;; +;; This program is free software: you can redistribute it and/or modify +;; it under the terms of the

Re: Signed archives

More questions: 1. Will hydra.gnu.org serve only signed .narinfo files? 2. If not, how can one opt out of verifying while using ‘guix substitute-binary’? Should we add an option to ‘guix package’ and ‘guix build’? 3. How does a user get Hydra’s public key? 4. Will the entire cache be sig

Re: Guix tutorial

> I wrote a basic guide[1] for contributors. It covers instalation and usage > of guix, and also writing simple recipes and contributing to the project. Thanks for spreading the word! > If you find unpolished corners, please, comment , and I'll update the > post. Here goes… > - Install guix . D

‘guix authenticate’: Throw to key `gcry-error' with args `(536871113)'.

The keypair was created this way: $ openssl genrsa -out ./cache-key.sec 2048 $ openssl rsa -in ./cache-key.sec -pubout > ./cache-key.pub All the tests pass. What’s wrong? $ guix authenticate rsautl -sign -inkey cache-key.sec -in 3r2n9zm3kxb28klpzgarjxj8x3y3y6wf.narinfo.hash Backtrace: In ice-9

Re: i686: recipe for target 'cc1plus' failed

> This is ‘master’? Yes. > Could it be an ENOMEM showing up above in the log? ranlib: libbackend.a: No space left on device It seems I should clean up my disk. How much space does IceCat need? pgpuOKvgFjP1m.pgp Description: PGP signature

i686: recipe for target 'cc1plus' failed

Can anyone reproduce this? g++ -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONF

Re: Signed archives

I’d like to see a signature in the wild. Are there any signed .narinfo files on hydra.nixos.org? I’ve checked GNU Hello [1]; it’s not signed. [1] http://hydra.nixos.org/6iqpvq3k2nlmfn3l59rsf3c57ji7jiyb.narinfo pgpTuQkQKLw91.pgp Description: PGP signature

Re: Symlinks to generic names

> Some software (rightly or wrongly) tries to build with "lex" and "yacc" . > Guix does not provide these. > Instead we have "flex" and "bison". Most operating systems have symbolic > links lex -> flex and yacc -> bison. > Shouldn't we provide these too? I guess this should solve the problem (

Re: Signed archives

Sorry, I’m failing to understand how the protocol works. Is the spec available somewhere? Could you describe the entire process in a step-by-step way? What does happen when the client requests a substitute? You mentioned that the client attempts to fetch the corresponding .narinfo file. What d

Signed archives (was: ‘guix archive’ doesn’t work over ‘./pre-inst-env’)

> Indeed. I just fixed that. Thanks! >> Also, where can I find the corresponding NAR info file? According to >> this commit [1], the signature should be there. > The .narinfo files are created on the fly. When looking for a binary > for /nix/store/x4mnd9747fgwacjrvl1rynh59qlgz8gh-coreutils-8.

‘guix archive’ doesn’t work over ‘./pre-inst-env’

$ sudo ./pre-inst-env guix archive --generate-key $ ./pre-inst-env guix archive --export hello > hello.nar error: executing `guix-authenticate': No such file or directory guix archive: error: build failed: program `guix-authenticate' failed with exit code 1 The command succeeded when I installed

Re: Guix initd script

> I wrote an initd script for starting guix-daemon and would like to > share it. It is available here: > https://gnunet.org/content/gnu-guix-initd-script Could you add a license header? pgpz2N9UVYWxf.pgp Description: PGP signature

Re: Package Definition Place

> Thanks, here are the results: > > gnu/packages/zsh.scm:12:2: warning: possibly unbound variable `mit' > > The license is like MIT. > > guix build: error: zsh: unknown package I guess it would be easier to help if you provide the code. pgpy4oI5TndsZ.pgp Description: PGP signature

Re: Package Definition Place

> Yes, I don't know where 'gnu/packages' is except for savannah. Hm, I’m a bit puzzled. How did you change ‘gnu-system.am’, then? ‘gnu/packages’ should be in the same directory (on your machine) as ‘gnu-system.am’. Did you clone the repository or download the tarball? If not, could you please f

Re: Package Definition Place

> make[2]: *** No rule to make target `gnu/packages/zsh.scm', needed by `all- > am'. Stop. Sorry, I totally misunderstood the context. Are you trying to add Zsh? It seems you added a line to ‘gnu-system.am’ but forgot to add a file to ‘gnu/packages’. Could you confirm? pgphZ6mz0EGJx.pgp Desc

Re: Package Definition Place

> Am I supposed to add a module to gnu-system.am? Yes, here’s an example [1]. > make[2]: *** No rule to make target `gnu/packages/zsh.scm', needed by `all- > am'. Stop. I’ve just tried the following. Could you do the same and report any issues? $ git clone git://git.sv.gnu.org/guix.git $ cd g

Re: FAIL: tests/guix-build.sh

> Eric reported a similar failure on IRC, with Guile 2.0.5, which I > believe is solved by de67926. Can you confirm? I couldn’t reproduce it earlier, so I can’t confirm. However, ‘make check TESTS=tests/guix-build.sh’ passes in HEAD. pgpBshU1nT3vk.pgp Description: PGP signature

GNU Aris doesn’t work properly

The attached recipe successfully builds, but the ‘test’ program segfaults, and the ‘aris’ program becomes unusable when you try to create a new file. I don’t have time to look through the build directory nor to build it outside of Guix right now, but I’ll do it later. As always, any help is appre

FAIL: tests/guix-build.sh

I got the following error, which I couldn’t reproduce (bf4211523baf8ab1c853aac48ef0324f8f704510). Is there a need to worry? + guix build hello -d + grep -e '-hello-[0-9\.]\+\.drv$' accepted connection from pid 15177, uid 1000 guix build: error: build failed: substituter `substitute-binary' died

Re: [PATCH] gnu: Add GNU APL.

> Do Readline and LAPACK show up in ‘guix gc --references $(guix build > apl)’? If they don’t, you can remove them. LAPACK doesn’t show up, but this line appears in the logs when it’s omitted: LApack.cc:410:2: warning: #warning liblapack not found or not installed. ⌹ will not work. [-Wcpp] >

[PATCH] gnu: Add GNU APL.

Even though ‘README-1-prerequisites’ states that LAPACK, Gettext, and Readline are needed, GNU APL successfully builds without them. Would you like to keep these inputs anyway? From b0f941b6c2ffd703d9a822c580356df4b6423c62 Mon Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Thu, 7 Nov 2013

Re: [PATCH] gnu: Add LAPACK.

>> May I push this patch to ‘master’? > Yep! Done. > (though I gather that the next upstream version of LAPACK will be > fixed, right?). I think so. > Two things we could do: (1) add a ‘snippet’ field in ‘origin’, which is > where the ‘remove-file’ calls would appear, (2) host a freed version

[PATCH] gnu: Add LAPACK. (was: LAPACK: tests fail; non-free files)

May I push this patch to ‘master’? Should (format #t "removing '~a'~%" file) be i18n’d? From 3e94fe1afc01d08997fd95775aab06c4495ba9d6 Mon Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Mon, 4 Nov 2013 18:58:54 + Subject: [PATCH] gnu: Add LAPACK. * gnu/packages/mat

Re: [PATCH] gnu: Add GCC front ends for Fortran, Go, Objective C, and Objective C++.

> ‘ld-wrapper’ is a wrapper around the linker that adds a -rpath argument > for each -l argument (see the top of ld-wrapper.scm), such that all the > needed libraries are in the resulting binary’s RUNPATH. Could you show how it helps to avoid the need to set environment variables? > Please add a

[PATCH] gnu: Add GCC front ends for Fortran, Go, Objective C, and Objective C++.

60e7d9d4a7592129c0369eee52b156170d1cf Mon Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Thu, 31 Oct 2013 19:54:36 + Subject: [PATCH] gnu: Add GCC front ends for Fortran, Go, Objective C, and Objective C++. * gnu/packages/gcc.scm (custom-gcc, gfortran-4.8, gccgo-4.8) (gcc-objc-4.8, gcc-

Re: GCC front-ends

> Argh, you also need (srfi srfi-26) for ‘cut’, sorry about that. Hm, I’ve added the module, but I still get the same error. pgp_x9KZwHIvm.pgp Description: PGP signature

Re: GCC front-ends

> That’s a bug, which may have been fixed in 4.8.2 no? I’d rather not > workaround that if it’s been/being fixed. No, it has not been fixed. Well, the previous patch didn’t contain any workarounds. However, users would have to pass ‘-g’ each time they decide to compile anything. Otherwise, the

[PATCH] gnu: gcc-4.8: Upgrade to 4.8.2.

May I push this patch to master? From 8bceb04eb5a7723eb988a164ee9ca8e7037d551f Mon Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Mon, 28 Oct 2013 16:44:26 + Subject: [PATCH] gnu: gcc-4.8: Upgrade to 4.8.2. * gnu/packages/gcc.scm (gcc-4.8): Upgrade to 4.8.2. --- gnu/packages/gcc.scm

Re: Important libffi bug fix for MIPS N32

> This line is: > ASSERT (st1.st_ctime < st2.st_ctime > || (st1.st_ctime == st2.st_ctime > && get_stat_ctime_ns (&st1) < get_stat_ctime_ns (&st2))); > (See > .) > Could it have someth

Re: [PATCH] gnu: cmake: Bump to 2.8.12

> Could you apply this patch and try to build lapack ? Thanks, it works. @ build-succeeded /nix/store/wyzcbhijr8ibk2rn3rxiiyq2hbrfrwqr-lapack-3.4.2.drv - /nix/store/gfzgj7ycqc1j8y094mma77ck4zbzvkf3-lapack-3.4.2 pgpVFYua9rj_k.pgp Description: PGP signature

Re: LAPACK: tests fail; non-free files

> I would suggest to add lapack only after the fortran compiler is in > master. Sure. But I won’t push the compiler without talking to Ludo. > You might wish to put the variable into maths.scm. OK. > Debian removes them: > > http://ftp-master.metadata.debian.org/changelogs/main/l/lapack/un

Re: Important libffi bug fix for MIPS N32

(Not sure why my previous messages weren’t signed.) >> Now, should I test the mentioned fix? > Yes, please do! The coreutils package fails to build: FAIL: test-fchownat (exit: 134) === test-chown.h:193: assertion failed […] == 1

Re: LAPACK: tests fail; non-free files

> (home-page "http://www.gnu.org/software/lapack/";) Oops, I’ll fix this. pgpmG10JlJOS3.pgp Description: PGP signature

LAPACK: tests fail; non-free files

ght © 2013 Nikita Karetnikov ;;; ;;; This file is part of GNU Guix. ;;; ;;; GNU Guix is free software; you can redistribute it and/or modify it ;;; under the terms of the GNU General Public License as published by ;;; the Free Software Foundation; either version 3 of the License, or (at ;;; your o

Re: Important libffi bug fix for MIPS N32

> A failing test in glib alerted me to a bug in libffi on MIPS N32. I've > pushed a fix[*] to the 'loongson' branch. It will require rebuilding > quite a few packages, so I recommend aborting whatever builds you have > running, and pulling the latest 'loongson' before continuing. I successfully

Re: Preliminary MIPS N32 port now available

First, I upgraded and tried again, but got the same error. Then, I defined SQLITE_DISABLE_DIRSYNC and got this one: stripping binaries in "/nix/store/1n843qz1psmp3bvx6hk1gj3mp1akdama-glibc-intermediate-2.18/sbin" with "strip" and flags ("--strip-debug") debugging output written to "/nix/store/

GCC front-ends (was: GFortran can’t find system headers)

> I guess this triggers a complete rebuild, right? (That means it would > go in ‘core-updates’.) > Using the ‘substitute-keyword-arguments’ hack as in base.scm would allow > you to avoid that. > Also, the ‘origin’ thing should be factorized: > (define (gcc-source version) > (origin ...))

Re: Preliminary MIPS N32 port now available

> I still think it's probably a good idea to switch away from JFS, since > you're likely to run into other problems like this, I see this as an opportunity to report problems. > but if you really > want to stick with JFS, compiling a newer version of SQLite and then > reconfiguring and rebuilding

Re: Preliminary MIPS N32 port now available

> I think your best option is to switch back to ext3 or ext4. Thanks, will do. I was told to switch to JFS to avoid ext-specific issues; I’m laughing out loud now, haha. pgpQ6EKF8J1gg.pgp Description: PGP signature

Re: Preliminary MIPS N32 port now available

I tried to build ‘hello’ twice, and the following error occurred each time: stripping binaries in "/nix/store/hl8khv4qip9nwbm1qm93irbz9has4wrd-gcc-cross-boot0-4.7.3/bin" with "strip" and flags ("--strip-debug") phase `strip' succeeded after 17 seconds error (ignored): aborting transaction: canno

Re: Preliminary MIPS N32 port now available

> If you own a 64-bit MIPS system (including Loongson 2F), are willing to > build everything on your own machine, and would like to try out the > preliminary port of Guix to MIPS N32, the "loongson" branch of the Guix > git repo is ready for your early testing. > If you run into a 'match-error', t

Re: GFortran can’t find system headers

> Instead, what should do is preserve the arguments; the value associated > with #:configure-flags should be changed to replace any > --enable-languages=.* flag with yours. See ‘gcc-boot0’ in base.scm for > how to do that. Are you talking about the ‘substitute-keyword-arguments’ part? > Alternat

GFortran can’t find system headers

I’m trying to package APL, which requires LAPACK, which requires Fortran. Here’s my attempt to add the last one: (define-public gfortran-4.8 (package (inherit gcc-4.8) (name "gfortran") (arguments `(#:configure-flags '("--enable-languages=fortran") I get the following error while t

[PATCH] doc: Improve the copyright notice.

Karl, thank you so much. I hope it’s OK now. Ludo, what do you think? From a384d93077e1dab066e0761a056b52fe1ba6dfd6 Mon Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Fri, 11 Oct 2013 15:52:27 + Subject: [PATCH] doc: Improve the copyright notice. --- doc/guix.texi | 55

Re: [PATCH] gnu: Add GNU acct.

> Yes, please! Done. By the way, thanks for showing the head of the file, it’s really helpful. > (Make sure ‘make sync-descriptions’ doesn’t complain.) There are other packages that complain. I’m willing to help with this. Which should be updated in ‘core-updates’? Will it be enough to run ‘g

Re: [PATCH] doc: Add 'copyrights' and 'license' macros.

ackage Managing packages with Guix. * guix build: (guix)Invoking guix build Building packages with Guix. @end direntry @titlepage @title GNU Guix Reference Manual @subtitle Using the GNU Guix Functional Package Manager @author Ludovic Courtès @author Andr

Re: a2ps: manpages fail to build

> It invokes /missing instead of $top_srcdir/build-aux/missing. >> I added ‘help2man’, but it didn’t help. > Could you check the configure log for clues? > Also, can you check the makefiles to see how it’s supposed to build the > man pages? It just needed Perl. >>> Rather use (substitute* (fin

[PATCH] gnu: Add GNU acct.

May I push this patch? From 20809203713f119ffaa0fb6d372b73cce5d1cf51 Mon Sep 17 00:00:00 2001 From: Nikita Karetnikov Date: Thu, 10 Oct 2013 10:32:15 + Subject: [PATCH] gnu: Add GNU acct. * gnu/packages/acct.scm: New file. * gnu-system.am (GNU_SYSTEM_MODULES): Add it. --- gnu-system.am

Re: a2ps: manpages fail to build

> There’s a bug in its build system, but most likely it wants ‘help2man’ > (as native input.) Could you expand on the bug part? I added ‘help2man’, but it didn’t help. > Rather use (substitute* (find-files "." ".*") ...) if that works. It takes too much time, or I’m doing something wrong. > No

a2ps: manpages fail to build

6cbfs2a539j38bndkm5zj-a2ps-4.14.drv' failed What’s wrong? Also, I don’t like the synopsis from Womb, so I used my own. Is it OK? ;;; GNU Guix --- Functional package management for GNU ;;; Copyright © 2013 Nikita Karetnikov ;;; ;;; This file is part of GNU Guix. ;;; ;;; GNU Guix is free

[PATCH] doc: Add 'copyrights' and 'license' macros.

:00 2001 From: Nikita Karetnikov Date: Wed, 9 Oct 2013 10:37:34 + Subject: [PATCH] doc: Add 'copyrights' and 'license' macros. * doc/guix.texi (YEARS): Remove it. (copyrights, license): Add these macros and use them. --- doc/guix.texi | 39 ---

  1   2   3   >