* Re: [Guix] FTBFS on Ubuntu (12.04) 64bit. Various fatal during install.
[not found] ` <87li5hb71f.fsf@gnu.org>
@ 2013-07-08 17:12 ` BlueT - Matthew Lien - 練喆明
2013-07-08 20:56 ` Ludovic Courtès
0 siblings, 1 reply; 12+ messages in thread
From: BlueT - Matthew Lien - 練喆明 @ 2013-07-08 17:12 UTC (permalink / raw)
To: guix-devel
[-- Attachment #1: Type: text/plain, Size: 3055 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2013年07月08日 19:55, Ludovic Courtès wrote:
> "BlueT - Matthew Lien - 練喆明" <bluet@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
Yes I do have those packages and files installed.
bluet@GuixOnUbuntu64:~$ dpkg -la|grep -P "(pkg-config|autoconf|guile)"
ii autoconf 2.68-1ubuntu2
automatic configure script builder
ii guile-2.0 2.0.5+1-1 GNU
extension language and Scheme interpreter
ii guile-2.0-dev 2.0.5+1-1
Development files for Guile 2.0
ii guile-2.0-libs 2.0.5+1-1 Core
Guile libraries
ii pkg-config 0.26-1ubuntu1
manage compile and link flags for libraries
bluet@GuixOnUbuntu64:~$ dpkg -L pkg-config |grep pkg.m4
/usr/share/aclocal/pkg.m4
>> 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>)
(log in attachment)
>> 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
Ok I'll test it once I can remove the blocker in Git version of Guix.
> 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. :-)
I see.
But I'd be more comfortable to see a software passed all tests before
installing it. :-P
> Thanks for testing!
Love to help FLOSS projects. :-)
But I think I'm kinda annoying to you about these bug/issue reports.
I almost feel I'm dumb 'coz I can't do more debugging/bug-fixing with
scheme.
Best wishes,
BlueT
- --
/ Just another [ Perl | FOSS | Security ] Hacker. /
/ BlueT = Matthew Lien = 練喆明 /
/ http://BlueT.org /
/ GPG: 4A293CBD /
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlHa8uwACgkQvRNvgEopPL1KbACePYZ1Adztt+KwjA5wOlS1XsLF
ZBQAn28i2N4rEe0iI6uYvkBLYDIax3BK
=Uz2s
-----END PGP SIGNATURE-----
[-- Attachment #2: utils.log --]
[-- Type: text/x-log, Size: 1434 bytes --]
%%%% Starting test utils
Group begin: utils
Test begin:
test-name: "bytevector->base16-string->bytevector"
Test end:
result-kind: pass
actual-value: #t
Test begin:
test-name: "gnu-triplet->nix-system"
Test end:
result-kind: pass
actual-value: #t
Test begin:
test-name: "package-name->name+version"
Test end:
result-kind: pass
actual-value: #t
Test begin:
test-name: "string-tokenize*"
Test end:
result-kind: pass
actual-value: (("foo") ("foo" "bar" "baz") ("foo" "bar" "") ("foo" "bar" "baz"))
expected-value: (("foo") ("foo" "bar" "baz") ("foo" "bar" "") ("foo" "bar" "baz"))
Test begin:
test-name: "fold2, 1 list"
Test end:
result-kind: pass
actual-value: ((4 3 2 1 0) (-4 -3 -2 -1 0))
expected-value: ((4 3 2 1 0) (-4 -3 -2 -1 0))
Test begin:
test-name: "fold2, 2 lists"
Test end:
result-kind: pass
actual-value: (((d . 3) (c . 2) (b . 1) (a . 0)) ((d . -3) (c . -2) (b . -1) (a . 0)))
expected-value: (((d . 3) (c . 2) (b . 1) (a . 0)) ((d . -3) (c . -2) (b . -1) (a . 0)))
Test begin:
test-name: "filtered-port, file"
Test end:
result-kind: fail
actual-value: #f
Test begin:
test-name: "filtered-port, non-file"
Test end:
result-kind: pass
actual-value: #t
Test begin:
test-name: "store-path-package-name"
Test end:
result-kind: pass
actual-value: "bash-4.2-p24"
expected-value: "bash-4.2-p24"
Group end: utils
# of expected passes 8
# of unexpected failures 1
[-- Attachment #3: test-suite.log --]
[-- Type: text/x-log, Size: 1963 bytes --]
====================================
GNU Guix 0.2: ./test-suite.log
====================================
# TOTAL: 18
# PASS: 16
# SKIP: 0
# XFAIL: 0
# FAIL: 2
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
FAIL: tests/utils
=================
%%%% Starting test utils (Writing full log to "utils.log")
%%%% Starting test utils (Writing full log to "utils.log")
%%%% Starting test utils (Writing full log to "utils.log")
FAIL filtered-port, file
%%%% Starting test utils (Writing full log to "utils.log")
FAIL filtered-port, file
%%%% Starting test utils (Writing full log to "utils.log")
FAIL filtered-port, file
%%%% Starting test utils (Writing full log to "utils.log")
FAIL filtered-port, file
;;; (#t)
# of expected passes 8
# of unexpected failures 1
FAIL: tests/packages
====================
accepted connection from pid 8099, uid 1000
%%%% Starting test packages (Writing full log to "packages.log")
;;; (name #<<location> file: "gnu/packages/bootstrap.scm" line: 188 column: 5>)
FAIL package-field-location
;;; (x (("b" #<package b-0 tests/packages.scm:80 347ea50>) ("b/a" #<package a-0 tests/packages.scm:79 347eb00>) ("c" #<package c-0 tests/packages.scm:82 347e9a0>) ("d" #<package d-0 tests/packages.scm:84 347e8f0>) ("d/x" "something.drv")))
;;; (drv "/home/bluet/guix-0.2/test-tmp/store/7w5b9ws1c8cp02qs8zrpv42jr5mrqk3x-trivial-0.drv" "/home/bluet/guix-0.2/test-tmp/store/7zp77r66a2m3n783r9asnf5760iv1v9r-trivial-0")
;;; (drv "/home/bluet/guix-0.2/test-tmp/store/b46mgjpwk2cyzm0v23wz8ap3rim5wb0r-trivial-with-input-file-0.drv" "/home/bluet/guix-0.2/test-tmp/store/scfyizrxvknsx1kcrqfiw7as9p9dal1a-trivial-with-input-file-0")
;;; (drv "/home/bluet/guix-0.2/test-tmp/store/zvrz1kqy8b9hy6ssllqjsr5dz3mswfjq-trivial-system-dependent-input-0.drv" "/home/bluet/guix-0.2/test-tmp/store/p9kiyvpm3nmxksng16zzmiy58fdcgxbg-trivial-system-dependent-input-0")
# of expected passes 11
# of unexpected failures 1
245 operations
[-- Attachment #4: packages.log --]
[-- Type: text/x-log, Size: 1421 bytes --]
%%%% Starting test packages
Group begin: packages
Test begin:
test-name: "package-field-location"
Test end:
result-kind: fail
actual-value: #f
Test begin:
test-name: "package-transitive-inputs"
Test end:
result-kind: pass
actual-value: #t
Test begin:
test-name: "return values"
Test end:
result-kind: pass
actual-value: #t
Test begin:
test-name: "package-output"
Test end:
result-kind: pass
actual-value: #t
Test begin:
test-name: "trivial"
Test end:
result-kind: pass
actual-value: #t
Test begin:
test-name: "trivial with local file as input"
Test end:
result-kind: pass
actual-value: #t
Test begin:
test-name: "trivial with system-dependent input"
Test end:
result-kind: pass
actual-value: #t
Test begin:
test-name: "search paths"
Test end:
result-kind: pass
actual-value: #t
Test begin:
test-name: "GNU Make, bootstrap"
Test end:
result-kind: pass
actual-value: #t
Test begin:
test-name: "fold-packages"
Test end:
result-kind: pass
actual-value: #<package hello-2.8 gnu/packages/base.scm:50 2d2c580>
expected-value: #<package hello-2.8 gnu/packages/base.scm:50 2d2c580>
Test begin:
test-name: "find-packages-by-name"
Test end:
result-kind: pass
actual-value: #t
Test begin:
test-name: "find-packages-by-name with version"
Test end:
result-kind: pass
actual-value: #t
Group end: packages
# of expected passes 11
# of unexpected failures 1
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [Guix] FTBFS on Ubuntu (12.04) 64bit. Various fatal during install.
2013-07-08 17:12 ` [Guix] FTBFS on Ubuntu (12.04) 64bit. Various fatal during install BlueT - Matthew Lien - 練喆明
@ 2013-07-08 20:56 ` Ludovic Courtès
2013-07-08 21:42 ` FAQ Nikita Karetnikov
0 siblings, 1 reply; 12+ messages in thread
From: Ludovic Courtès @ 2013-07-08 20:56 UTC (permalink / raw)
To: BlueT - Matthew Lien - 練喆明; +Cc: guix-devel
"BlueT - Matthew Lien - 練喆明" <bluet@bluet.org> skribis:
> On 2013年07月08日 19:55, Ludovic Courtès wrote:
>> "BlueT - Matthew Lien - 練喆明" <bluet@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’.
^ permalink raw reply [flat|nested] 12+ messages in thread
* FAQ
2013-07-08 20:56 ` Ludovic Courtès
@ 2013-07-08 21:42 ` Nikita Karetnikov
2013-07-09 11:21 ` FAQ Ludovic Courtès
0 siblings, 1 reply; 12+ messages in thread
From: Nikita Karetnikov @ 2013-07-08 21:42 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: guix-devel
[-- Attachment #1: Type: text/plain, Size: 309 bytes --]
> 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
I've seen similar questions several times. Maybe we should create a FAQ
section in 'HACKING'. What do you think?
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: FAQ
2013-07-08 21:42 ` FAQ Nikita Karetnikov
@ 2013-07-09 11:21 ` Ludovic Courtès
2013-07-09 19:00 ` FAQ Nikita Karetnikov
0 siblings, 1 reply; 12+ messages in thread
From: Ludovic Courtès @ 2013-07-09 11:21 UTC (permalink / raw)
To: Nikita Karetnikov; +Cc: guix-devel
Nikita Karetnikov <nikita@karetnikov.org> skribis:
>> 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
>
> I've seen similar questions several times. Maybe we should create a FAQ
> section in 'HACKING'. What do you think?
It’s a good idea, probably as the first section in ‘HACKING’. Would you
like to propose a patch?
Thanks,
Ludo’.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: FAQ
2013-07-09 11:21 ` FAQ Ludovic Courtès
@ 2013-07-09 19:00 ` Nikita Karetnikov
2013-07-09 20:03 ` FAQ Ludovic Courtès
0 siblings, 1 reply; 12+ messages in thread
From: Nikita Karetnikov @ 2013-07-09 19:00 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: guix-devel
[-- Attachment #1.1: Type: text/plain, Size: 160 bytes --]
> It’s a good idea, probably as the first section in ‘HACKING’. Would you
> like to propose a patch?
Attached. Did I forget to mention anything?
[-- Attachment #1.2: 0001-doc-Add-FAQ-to-HACKING.patch --]
[-- Type: text/x-diff, Size: 1667 bytes --]
From 17a11ca78a4f71174edf57ec01f55934b1761363 Mon Sep 17 00:00:00 2001
From: Nikita Karetnikov <nikita@karetnikov.org>
Date: Tue, 9 Jul 2013 18:47:17 +0000
Subject: [PATCH] doc: Add FAQ to 'HACKING'.
---
HACKING | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/HACKING b/HACKING
index dd59a68..89ea124 100644
--- a/HACKING
+++ b/HACKING
@@ -3,12 +3,32 @@
#+TITLE: Hacking GNU Guix and Its Incredible Distro
Copyright © 2012, 2013 Ludovic Courtès <ludo@gnu.org>
+Copyright © 2013 Nikita Karetnikov <nikita@karetnikov.org>
Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved.
+* FAQ
+
+** ./configure: line 6755: `PKG_CHECK_MODULES(GUILE, guile-2.0 >= 2.0.5)'
+
+This message means that Autoconf didn't pick up the definition of the
+'PKG_CHECK_MODULES' M4 macro. 'pkg.m4' is provided by the 'pkg-config'
+package. If you install 'pkg-config', Autoconf should automatically find it.
+
+However, if you installed Automake in '/usr/local', it wouldn't look for '.m4'
+files in '/usr/share'. You have to invoke the following command in that case:
+
+ $ export ACLOCAL_PATH=/usr/share/aclocal
+
+** make: *** No rule to make target `nix/libstore/schema.sql', needed by
+`nix/libstore/schema.sql.hh'.
+
+You must run './bootstrap', which just invokes 'git submodule update', before
+'./configure && make && make check'.
+
* Running Guix before it is installed
Command-line tools can be used even if you have not run "make install".
--
1.7.9.5
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
^ permalink raw reply related [flat|nested] 12+ messages in thread
* Re: FAQ
2013-07-09 19:00 ` FAQ Nikita Karetnikov
@ 2013-07-09 20:03 ` Ludovic Courtès
2013-07-09 20:26 ` FAQ Nikita Karetnikov
0 siblings, 1 reply; 12+ messages in thread
From: Ludovic Courtès @ 2013-07-09 20:03 UTC (permalink / raw)
To: Nikita Karetnikov; +Cc: guix-devel
Nikita Karetnikov <nikita@karetnikov.org> skribis:
>> It’s a good idea, probably as the first section in ‘HACKING’. Would you
>> like to propose a patch?
>
> Attached. Did I forget to mention anything?
Looks good, but I would call it “Building from Git”, for instance, with
this particular error as a caveat.
> +You must run './bootstrap', which just invokes 'git submodule update', before
Remove “just”.
I would also link to the “Installation” section of the manual, and to
“Installing Guix from Guix” in README.
WDYT?
Ludo’.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: FAQ
2013-07-09 20:03 ` FAQ Ludovic Courtès
@ 2013-07-09 20:26 ` Nikita Karetnikov
2013-07-09 22:39 ` FAQ Ludovic Courtès
0 siblings, 1 reply; 12+ messages in thread
From: Nikita Karetnikov @ 2013-07-09 20:26 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: guix-devel
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
> Looks good, but I would call it “Building from Git”, for instance, with
> this particular error as a caveat.
OK.
> Remove “just”.
OK.
> I would also link to the “Installation” section of the manual, and to
> “Installing Guix from Guix” in README.
> WDYT?
Can I use 'README' instead of 'HACKING', then? All installation
instructions are there.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: FAQ
2013-07-09 20:26 ` FAQ Nikita Karetnikov
@ 2013-07-09 22:39 ` Ludovic Courtès
2013-07-10 6:35 ` FAQ Nikita Karetnikov
0 siblings, 1 reply; 12+ messages in thread
From: Ludovic Courtès @ 2013-07-09 22:39 UTC (permalink / raw)
To: Nikita Karetnikov; +Cc: guix-devel
Nikita Karetnikov <nikita@karetnikov.org> skribis:
>> Looks good, but I would call it “Building from Git”, for instance, with
>> this particular error as a caveat.
>
> OK.
>
>> Remove “just”.
>
> OK.
>
>> I would also link to the “Installation” section of the manual, and to
>> “Installing Guix from Guix” in README.
>
>> WDYT?
>
> Can I use 'README' instead of 'HACKING', then? All installation
> instructions are there.
I’d say no, because that could lead “normal users” to think they need
Automake & co. to install Guix.
Ludo’.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: FAQ
2013-07-09 22:39 ` FAQ Ludovic Courtès
@ 2013-07-10 6:35 ` Nikita Karetnikov
2013-07-10 13:28 ` FAQ Ludovic Courtès
0 siblings, 1 reply; 12+ messages in thread
From: Nikita Karetnikov @ 2013-07-10 6:35 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: guix-devel
[-- Attachment #1.1: Type: text/plain, Size: 144 bytes --]
> I’d say no, because that could lead “normal users” to think they need
> Automake & co. to install Guix.
OK, can I push this one?
[-- Attachment #1.2: 0001-doc-Add-Building-from-Git-to-HACKING.patch --]
[-- Type: text/x-diff, Size: 2252 bytes --]
From cb6750a9869fc162d98eeb38ccb78e0846553f64 Mon Sep 17 00:00:00 2001
From: Nikita Karetnikov <nikita@karetnikov.org>
Date: Wed, 10 Jul 2013 06:13:59 +0000
Subject: [PATCH] doc: Add "Building from Git" to 'HACKING'.
---
HACKING | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/HACKING b/HACKING
index 9d8960c..8f6e835 100644
--- a/HACKING
+++ b/HACKING
@@ -3,12 +3,42 @@
#+TITLE: Hacking GNU Guix and Its Incredible Distro
Copyright © 2012, 2013 Ludovic Courtès <ludo@gnu.org>
+Copyright © 2013 Nikita Karetnikov <nikita@karetnikov.org>
Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved.
+* Building from Git
+
+The following errors might appear if you are building from Git. Also,
+take a look at the [[https://gnu.org/software/guix/manual/guix.html#Installation]["Installation"]] section of the manual and the
+[[http://git.savannah.gnu.org/cgit/guix.git/tree/README]["Installing Guix from Guix"]] section in 'README'.
+
+** ./configure: line 6755: `PKG_CHECK_MODULES(GUILE, guile-2.0 >= 2.0.5)'
+
+This message means that Autoconf didn't pick up the definition of the
+'PKG_CHECK_MODULES' M4 macro. 'pkg.m4' is provided by the 'pkg-config'
+package. If you install 'pkg-config', Autoconf should automatically find it.
+
+However, if you installed Automake in '/usr/local', it wouldn't look for '.m4'
+files in '/usr/share'. You have to invoke the following command in that case:
+
+ $ export ACLOCAL_PATH=/usr/share/aclocal
+
+** make: *** No rule to make target `nix/libstore/schema.sql', needed by
+`nix/libstore/schema.sql.hh'.
+
+You must run './bootstrap', which invokes 'git submodule update', before
+'./configure && make && make check'.
+
+** /bin/bash: dot: command not found
+make[2]: *** [doc/images/bootstrap-graph.png] Error 127
+
+You must install Graphviz. (It is not listed as a requirement because the
+resulting images will be shipped with a tarball.)
+
* Running Guix before it is installed
Command-line tools can be used even if you have not run "make install".
--
1.7.9.5
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
^ permalink raw reply related [flat|nested] 12+ messages in thread
* Re: FAQ
2013-07-10 6:35 ` FAQ Nikita Karetnikov
@ 2013-07-10 13:28 ` Ludovic Courtès
2013-07-12 20:50 ` FAQ Nikita Karetnikov
0 siblings, 1 reply; 12+ messages in thread
From: Ludovic Courtès @ 2013-07-10 13:28 UTC (permalink / raw)
To: Nikita Karetnikov; +Cc: guix-devel
Nikita Karetnikov <nikita@karetnikov.org> skribis:
> +* Building from Git
> +
> +The following errors might appear if you are building from Git. Also,
> +take a look at the [[https://gnu.org/software/guix/manual/guix.html#Installation]["Installation"]] section of the manual and the
> +[[http://git.savannah.gnu.org/cgit/guix.git/tree/README]["Installing Guix from Guix"]] section in 'README'.
Sorry if I wasn’t clear. What I meant is: instead of presenting it as a
trial-and-error approach, I would rather present it as a sequence of
instructions to build from Git.
Something like:
First, make sure Autoconf (>= 2.69), Automake, pkg-config, etc. are
installed. If you get an error like this:
./configure: line 6755: `PKG_CHECK_MODULES(GUILE, guile-2.0 >= 2.0.5)'
then it probably means that pkg-config’s pkg.m4 file was not found by
Automake. Make sure pkg.m4 is available, and possibly add its
directory to the ACLOCAL_PATH environment variable (info "(automake)
Macro Search Path").
Second, run ./bootstrap. Among other things, this will run ‘git
submodule update’. If you get an error like this:
...
Also, when referring to a GNU manual, please show the info command (as I
did above) rather than giving a hyperlink. This will ensure that users
read the right version of the manual.
For the link to README, just use [[./README][README]] (info "(org)
Hyperlinks").
It may look like I’m being picky, and indeed that’s what I am ;-), but I
think it’s important to agree on how to present information.
Thanks for your help!
Ludo’.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: FAQ
2013-07-10 13:28 ` FAQ Ludovic Courtès
@ 2013-07-12 20:50 ` Nikita Karetnikov
2013-07-12 21:41 ` FAQ Ludovic Courtès
0 siblings, 1 reply; 12+ messages in thread
From: Nikita Karetnikov @ 2013-07-12 20:50 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: guix-devel
[-- Attachment #1.1: Type: text/plain, Size: 640 bytes --]
> Sorry if I wasn’t clear. What I meant is: instead of presenting it as a
> trial-and-error approach, I would rather present it as a sequence of
> instructions to build from Git.
OK, what do you think about this patch?
> For the link to README, just use [[./README][README]] (info "(org)
> Hyperlinks").
I decided not to refer to 'README' because it's mentioned in the
"Installation" section of the manual.
> It may look like I’m being picky, and indeed that’s what I am ;-), but I
> think it’s important to agree on how to present information.
No, you are absolutely right. Do you have any other comments?
[-- Attachment #1.2: 0001-doc-Add-Building-from-Git-to-HACKING.patch --]
[-- Type: text/x-diff, Size: 2364 bytes --]
From 64f56139dc2b3d92cf9b580414df609fdd951bf0 Mon Sep 17 00:00:00 2001
From: Nikita Karetnikov <nikita@karetnikov.org>
Date: Fri, 12 Jul 2013 20:31:28 +0000
Subject: [PATCH] doc: Add "Building from Git" to 'HACKING'.
---
HACKING | 35 +++++++++++++++++++++++++++++++++++
1 file changed, 35 insertions(+)
diff --git a/HACKING b/HACKING
index 9d8960c..c711521 100644
--- a/HACKING
+++ b/HACKING
@@ -3,12 +3,47 @@
#+TITLE: Hacking GNU Guix and Its Incredible Distro
Copyright © 2012, 2013 Ludovic Courtès <ludo@gnu.org>
+Copyright © 2013 Nikita Karetnikov <nikita@karetnikov.org>
Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved.
+* Building from Git
+
+First, make sure that 'autoconf' (>= 2.69), 'automake', and 'pkg-config' are
+installed. Run './bootstrap' that, among other things, invokes 'git submodule
+update', or you might get the following error
+
+ make: *** No rule to make target `nix/libstore/schema.sql', needed by
+ `nix/libstore/schema.sql.hh'
+
+Then, as always, run './configure'. If you get an error like this one
+
+ ./configure: line 6755: `PKG_CHECK_MODULES(GUILE, guile-2.0 >= 2.0.5)'
+
+it probably means that 'autoconf' couldn't find 'pkg.m4', which is provided by
+'pkg-config'. Make sure that 'pkg.m4' is available. For instance, if you
+installed 'automake' in '/usr/local', it wouldn't look for '.m4' files in
+'/usr/share'. So you have to invoke the following command in that case
+
+ $ export ACLOCAL_PATH=/usr/share/aclocal
+
+See "info '(automake) Macro Search Path'" for more information.
+
+After that you should proceed with 'make'. You might also get this error
+
+ /bin/bash: dot: command not found
+ make[2]: *** [doc/images/bootstrap-graph.png] Error 127
+
+This one is easy to handle; just install 'graphviz'. It is not listed as a
+requirement because the resulting images should come with a tarball.
+
+Finally, you have to invoke 'make check' to run tests. If anything fails,
+take a look at "info '(guix) Installation'" or send a message to
+<bug-guix@gnu.org>.
+
* Running Guix before it is installed
Command-line tools can be used even if you have not run "make install".
--
1.7.9.5
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
^ permalink raw reply related [flat|nested] 12+ messages in thread
* Re: FAQ
2013-07-12 20:50 ` FAQ Nikita Karetnikov
@ 2013-07-12 21:41 ` Ludovic Courtès
0 siblings, 0 replies; 12+ messages in thread
From: Ludovic Courtès @ 2013-07-12 21:41 UTC (permalink / raw)
To: Nikita Karetnikov; +Cc: guix-devel
Nikita Karetnikov <nikita@karetnikov.org> skribis:
>> Sorry if I wasn’t clear. What I meant is: instead of presenting it as a
>> trial-and-error approach, I would rather present it as a sequence of
>> instructions to build from Git.
>
> OK, what do you think about this patch?
Looks good to me!
One last thing:
> +* Building from Git
> +
> +First, make sure that 'autoconf' (>= 2.69), 'automake', and 'pkg-config' are
When speaking of the packages, not the commands, use the right spelling,
without quotes: Autoconf, Automake, pkg-config, Graphviz.
(When you do need quotation marks, you can use Unicode quotation marks.)
Please commit with these changes.
Thanks,
Ludo’.
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2013-07-12 21:47 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <51D71116.3080403@BlueT.org>
[not found] ` <87txk8sqc6.fsf@gnu.org>
[not found] ` <51D768DE.90403@BlueT.org>
[not found] ` <878v1jstco.fsf@gnu.org>
[not found] ` <51D9F8EF.5050806@BlueT.org>
[not found] ` <87li5hb71f.fsf@gnu.org>
2013-07-08 17:12 ` [Guix] FTBFS on Ubuntu (12.04) 64bit. Various fatal during install BlueT - Matthew Lien - 練喆明
2013-07-08 20:56 ` Ludovic Courtès
2013-07-08 21:42 ` FAQ Nikita Karetnikov
2013-07-09 11:21 ` FAQ Ludovic Courtès
2013-07-09 19:00 ` FAQ Nikita Karetnikov
2013-07-09 20:03 ` FAQ Ludovic Courtès
2013-07-09 20:26 ` FAQ Nikita Karetnikov
2013-07-09 22:39 ` FAQ Ludovic Courtès
2013-07-10 6:35 ` FAQ Nikita Karetnikov
2013-07-10 13:28 ` FAQ Ludovic Courtès
2013-07-12 20:50 ` FAQ Nikita Karetnikov
2013-07-12 21:41 ` FAQ Ludovic Courtès
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).