Re: [Guix] FTBFS on Ubuntu (12.04) 64bit. Various fatal during install.

[Ludovic Courtès]

"BlueT - Matthew Lien - 練喆明" <address@hidden> skribis:

> Now the bootstraping process passed, but ./configure seems to have
> syntax error.
>
> checking for the Guix system type... x86_64-linux
> ./configure: line 6755: syntax error near unexpected token `GUILE,'
> ./configure: line 6755: `PKG_CHECK_MODULES(GUILE, guile-2.0 >= 2.0.5)'

Yes, you need to have pkg.m4, as provided by pkg-config, in the
ACLOCAL_PATH.

  http://lists.gnu.org/archive/html/bug-guix/2013-06/msg00037.html

> 2. guix-0.2
>
>> Could you run this from the build directory:
>>
>>   rm -rf test-tmp && umask 0022 && make check
>>
>> With umask == 0002, the daemon can end up creating group-writable files,
>> which then triggers the above error.
>
> With umask 0022, fatal errors reduced to 2.

Great.  I’ll change ‘test-env’ to set umask before running the daemon.

> Test begin:
>   test-name: "package-field-location"
> Test end:
>   result-kind: fail
>   actual-value: #f

You’re using Guile 2.0.5, right?

Can you try the patch below, run ‘make check’,
and report the “;;; (name” and “;;; (version” lines from test-suite.log?

diff --git a/tests/packages.scm b/tests/packages.scm
index a4bb7fb..2d3ff89 100644
--- a/tests/packages.scm
+++ b/tests/packages.scm
@@ -70,9 +70,9 @@
             (goto port line column)
             (read port))))))
 
-    (and (equal? (read-at (package-field-location %bootstrap-guile 'name))
+    (and (equal? (read-at (pk 'name (package-field-location %bootstrap-guile 
'name)))
                  (package-name %bootstrap-guile))
-         (equal? (read-at (package-field-location %bootstrap-guile 'version))
+         (equal? (read-at (pk 'version (package-field-location 
%bootstrap-guile 'version)))
                  (package-version %bootstrap-guile))
          (not (package-field-location %bootstrap-guile 'does-not-exist)))))

> Test begin:
>   test-name: "filtered-port, file"
> Test end:
>   result-kind: fail
>   actual-value: #f

I believe this has been fixed:

  http://lists.gnu.org/archive/html/bug-guix/2013-07/msg00031.html

Note that it’s safe to install Guix at this point.  From there you’ll be
able to just run ‘guix pull’ to upgrade to the latest Guix from ‘master’.
Incidentally, you’ll be able to actually use it to install packages.  :-)

Thanks for testing!

Ludo’.