all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 28347@debbugs.gnu.org
Subject: [bug#28347] Cadaver
Date: Wed, 20 Sep 2017 19:35:17 +0300	[thread overview]
Message-ID: <878th9nxa2.fsf@gmail.com> (raw)
In-Reply-To: <87h8vyv0sn.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 19 Sep 2017 23:25:12 +0200")

Ludovic Courtès (2017-09-19 23:25 +0200) wrote:

> Alex Kost <alezost@gmail.com> skribis:
>
>> Ouch, so 0.30.2 is not supported.  This is the line from "configure.ac":
>>
>>   NE_REQUIRE_VERSIONS([0], [27 28 29])
>>
>> OK, I tried to build it with 0.30.2 anyway using the following phase:
>>
>>          (add-after 'unpack 'fix-required-neon-version
>>            (lambda _
>>              (substitute* "configure"
>>                (("27 28 29")
>>                 ,(string-join
>>                   (cdr (string-split (package-version neon) #\.))
>>                   ".")))
>>              #t))
>>
>> But I got:
>>
>>   configure: incompatible neon library version 0.30.2: wanted 0.30.2
>>   configure: using bundled neon (0.29.1)
>
> In ‘configure’, I think you need to replace “27 28 29” with “30”, not
> “30.2”, because of the way NEON_CHECK_VERSION in m4/neon.m4 matches
> versions:
>
>        for v in ne_require_minor; do
>           case $ne_libver in
>           ne_require_major.$v.*) ne_cv_lib_neonver=yes ;;
>           esac
>        done

Yeah, I tried to use "30", but it failed as well.

> I’m sure you’re almost there.  :-)

Actually, I don't have a wish to continue, sorry :-)

-- 
Alex

  reply	other threads:[~2017-09-20 16:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-04 18:11 [bug#28347] Cadaver ng0
2017-09-19 16:43 ` Alex Kost
2017-09-19 18:17   ` ng0
2017-09-19 21:25   ` Ludovic Courtès
2017-09-20 16:35     ` Alex Kost [this message]
2017-09-28 15:53   ` bug#28347: Cadaver Alex Kost

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

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

  git send-email \
    --in-reply-to=878th9nxa2.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=28347@debbugs.gnu.org \
    --cc=ludo@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.