From: Vincent Legoll <vincent.legoll@gmail.com>
To: Emmanuel Medernach <emmanuel.medernach@gmail.com>,
help-guix <help-guix@gnu.org>
Subject: Re: Problem compiling boost for mysql
Date: Thu, 14 May 2020 11:56:29 +0200 [thread overview]
Message-ID: <280b9e50-ddc4-a3ec-9ee5-b7445a4ce308@gmail.com> (raw)
In-Reply-To: <CAC_pKx9eMS2Bz=6r1V8q6UPjGPiVXzNGWk74rLnChU0z7iJ22w@mail.gmail.com>
Hello Emmanuel,
On 14/05/2020 09:50, Emmanuel Medernach wrote:
> I have an error when trying to build a package, the following
> gnu packages derivation does not compile:
>
> # guix build -e '(@ (gnu packages boost) boost-for-mysql)'
I'm reproducing the problem, I tried to use boost instead of
boost-for-mysql in the mysql package, but is still requires boost
1.59.0, which is not building.
First because execunix.c got translated into C++, in a later version of
boost, so the guix recipe to build it changed, see:
02fef9619bd96086aa9255ffb0944d4cda617c84
But boost-for-mysql inherits that configure phase, whereas it still has
the c version of that file.
And second, if you fix^Whack that, then you get a compilation error on
some const * being used as non-const *.
Here is that whitespace-damaged hack:
diff --git a/gnu/packages/boost.scm b/gnu/packages/boost.scm
index 2f2ca289ab..a9b463ca92 100644
--- a/gnu/packages/boost.scm
+++ b/gnu/packages/boost.scm
@@ -122,7 +124,7 @@
(out (assoc-ref outputs "out")))
(substitute* '("libs/config/configure"
"libs/spirit/classic/phoenix/test/runtest.sh"
- "tools/build/src/engine/execunix.cpp"
+ "tools/build/src/engine/execunix.c"
"tools/build/src/engine/Jambase")
(("/bin/sh") (which "sh")))
I don't know how to fix that properly, maybe copy/paste the whole
(arguments ...) from boost into boost-for-mysql, but that does not
look right.
--
Vincent Legoll
prev parent reply other threads:[~2020-05-14 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 7:50 Problem compiling boost for mysql Emmanuel Medernach
2020-05-14 9:56 ` Vincent Legoll [this message]
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=280b9e50-ddc4-a3ec-9ee5-b7445a4ce308@gmail.com \
--to=vincent.legoll@gmail.com \
--cc=emmanuel.medernach@gmail.com \
--cc=help-guix@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.
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).