"BlueT - Matthew Lien - 練喆明" <bl...@bluet.org> skribis:
> On 2013年07月08日 19:55, Ludovic Courtès wrote: >> "BlueT - Matthew Lien - 練喆明" <bl...@bluet.org> skribis: >>> 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 [...] > bluet@GuixOnUbuntu64:~$ dpkg -L pkg-config |grep pkg.m4 > /usr/share/aclocal/pkg.m4 Yes, but the Automake you installed by hand (in /usr/local I suppose?) doesn’t look for .m4 files under /usr/share. Thus you need to: export ACLOCAL PATH=/usr/share/aclocal >>> 2. guix-0.2 >>> Test begin: >>> test-name: "package-field-location" >>> Test end: >>> result-kind: fail >>> actual-value: #f >> >> You’re using Guile 2.0.5, right? > > bluet@GuixOnUbuntu64:~$ guile --version|head -n 1 > guile (GNU Guile) 2.0.5-deb+1-1 > >> Can you try the patch below, run ‘make check’, >> and report the “;;; (name” and “;;; (version” lines from test-suite.log? > > Hmmm there's no line with keyword 'version'. > > bluet@GuixOnUbuntu64:~/guix-0.2$ grep -P "(name|ver)" test-suite.log > ;;; (name #<<location> file: "gnu/packages/bootstrap.scm" line: 188 > column: 5>) This should be addressed by commit ee48b28. (It’s a harmless issue that would only make the source location in messages reported by ‘guix refresh’ slightly less precise.) Thanks, Ludo’.
