unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "BlueT - Matthew Lien - 練喆明" <bluet@bluet.org>
Cc: guix-devel@gnu.org
Subject: Re: [Guix] FTBFS on Ubuntu (12.04) 64bit. Various fatal during install.
Date: Mon, 08 Jul 2013 22:56:16 +0200	[thread overview]
Message-ID: <871u78ahzj.fsf@gnu.org> (raw)
In-Reply-To: <51DAF2F0.5020100@BlueT.org> ("BlueT - Matthew Lien - \=\?utf-8\?B\?57e05ZaG5piOIidz\?\= message of "Tue, 09 Jul 2013 01:12:16 +0800")

"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’.

  reply	other threads:[~2013-07-08 21:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871u78ahzj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bluet@bluet.org \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).