|
From: | Andreas Enge |
Subject: | Re: 'guix-build' returns 'unknown package', Bison's testsuite fails |
Date: | Sat, 26 Jan 2013 18:21:33 +0100 |
User-agent: | KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; ) |
Am Samstag, 26. Januar 2013 schrieb Nikita Karetnikov: > I'm trying to package 'gobject-introspection', but I'm facing some > problems: > 1. 'guix-build' doesn't work for new packages; it returns > "<package>: unknown package." I'm using the '-e' option as a > workaround, but it's not very convenient. > > For instance, if I copy the recipe for 'sed' to 'newsed.scm', then > replace 'sed' with 'newsed' in that file, and try to build it via > 'guix-build newsed', it will return the mentioned error message. > However, it will work if I use the '-e' option. Also, I won't get > any errors if I try to import it in the REPL. > > 2. Bison's testsuite fails and I'm not able to fix it. So I'd like to > disable it because I want to test 'gobject-introspection'. Why > doesn't '(arguments `(#:tests? #f))' disable the testsuite? > > These issues may seem unrelated, but there is a similarity: My changes > have no effect. I've just replaced 'gnu/packages/bison.scm' with an > empty file, but 'guix-build bison' doesn't raise any errors. Is it > related?
That has happened to me before when I forgot to execute "make install" or to add a file to Makefile.am.
Also, after deleting a file, it is not deleted from $PREFIX/share/...; in this way, it has happened to me that I had two versions of a package, one from a deleted/renamed file, one from the file with the new name; and the wrong one was built...
Andreas
|
[Prev in Thread] | Current Thread | [Next in Thread] |