From: Leo Famulari <leo@famulari.name>
To: 33605@debbugs.gnu.org
Subject: bug#33605: ncmpcpp and innoextract build when Boost is built with C++14
Date: Tue, 4 Dec 2018 16:45:30 -0500 [thread overview]
Message-ID: <20181204214530.GA1540@jasmine.lan> (raw)
In-Reply-To: <20181204002746.GA29184@jasmine.lan>
[-- Attachment #1.1: Type: text/plain, Size: 115 bytes --]
Building Boost with C++14 fixes the build failures of ncmpcpp and
innoextract. Patch attached.
What should we do?
[-- Attachment #1.2: 0001-gnu-Boost-Build-with-C-14.patch --]
[-- Type: text/plain, Size: 816 bytes --]
From 90f990416040d240a68d672fc8ac05b1adc50b8a Mon Sep 17 00:00:00 2001
From: Leo Famulari <leo@famulari.name>
Date: Tue, 4 Dec 2018 16:39:28 -0500
Subject: [PATCH] gnu: Boost: Build with C++14.
* gnu/packages/boost.scm (boost)[arguments]: Pass 'cxxflags=-std=c++14'
to #:make-flags.
---
gnu/packages/boost.scm | 1 +
1 file changed, 1 insertion(+)
diff --git a/gnu/packages/boost.scm b/gnu/packages/boost.scm
index b772781f5..f5c2c5830 100644
--- a/gnu/packages/boost.scm
+++ b/gnu/packages/boost.scm
@@ -67,6 +67,7 @@
`(#:tests? #f
#:make-flags
(list "threading=multi" "link=shared"
+ "cxxflags=-std=c++14"
;; Set the RUNPATH to $libdir so that the libs find each other.
(string-append "linkflags=-Wl,-rpath="
--
2.19.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-12-04 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 0:27 bug#33605: ncmpcpp fails to build with Boost 1.68.0 Leo Famulari
2018-12-04 21:45 ` Leo Famulari [this message]
2018-12-05 15:14 ` bug#33605: ncmpcpp and innoextract build when Boost is built with C++14 Marius Bakke
2018-12-05 19:18 ` Leo Famulari
2018-12-05 6:03 ` bug#33605: Boost 1.68.0 seems to require C++14 for libboost_system Leo Famulari
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=20181204214530.GA1540@jasmine.lan \
--to=leo@famulari.name \
--cc=33605@debbugs.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).