From: Alex Kost <alezost@gmail.com>
To: ng0 <ng0@infotropique.org>
Cc: 28347@debbugs.gnu.org
Subject: [bug#28347] Cadaver
Date: Tue, 19 Sep 2017 19:43:08 +0300 [thread overview]
Message-ID: <87mv5qbpwj.fsf@gmail.com> (raw)
In-Reply-To: <20170904181113.36ybxr5hrn36ywly@abyayala> (ng0@infotropique.org's message of "Mon, 4 Sep 2017 18:11:13 +0000")
ng0 (2017-09-04 18:11 +0000) wrote:
> A package from my "crypt". I tried various ways
> to unbundle neon but did not succeed.
I think it would be good if you wrote what you tried :-)
Here are my attempts:
At first, there are the following messages during "configure" phase:
configure: no external neon library found
configure: using bundled neon (0.29.1)
So, when I added ("neon" ,neon) input, I got:
configure: incompatible neon library version 0.30.2: wanted 0.27 28 29
configure: using bundled neon (0.29.1)
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)
What? Well, now I don't know what to do (perhaps I should have patched
"configure.ac" instead and added "autoreconf" phase, but I didn't try).
> The package itself works.
Great, I think if there will be no comments in a week or so, I will just
go ahead and commit your patch (in a hope this unbundling will happen in
the future somehow). So if anyone has something to say about this
patch, please do it now :-)
--
Alex
next prev parent reply other threads:[~2017-09-19 16:44 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 [this message]
2017-09-19 18:17 ` ng0
2017-09-19 21:25 ` Ludovic Courtès
2017-09-20 16:35 ` Alex Kost
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=87mv5qbpwj.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=28347@debbugs.gnu.org \
--cc=ng0@infotropique.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.