From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: Re: 'guix-build' returns 'unknown package', Bison's testsuite fails Date: Sat, 26 Jan 2013 18:21:33 +0100 Message-ID: <201301261821.33888.andreas@enge.fr> References: <87sj5ot7he.fsf@karetnikov.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="Boundary-01=_dCBBRoX20BY4qC0" Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:49079) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tz9Ro-0000ZB-BZ for bug-guix@gnu.org; Sat, 26 Jan 2013 12:21:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tz9Rk-0003ZW-0K for bug-guix@gnu.org; Sat, 26 Jan 2013 12:21:44 -0500 Received: from moutng.kundenserver.de ([212.227.17.10]:57564) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tz9Rj-0003Z1-M2 for bug-guix@gnu.org; Sat, 26 Jan 2013 12:21:39 -0500 In-Reply-To: <87sj5ot7he.fsf@karetnikov.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: bug-guix@gnu.org --Boundary-01=_dCBBRoX20BY4qC0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit 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 > ": 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 --Boundary-01=_dCBBRoX20BY4qC0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 7bit

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

--Boundary-01=_dCBBRoX20BY4qC0--