From: ludo@gnu.org (Ludovic Courtès)
To: Marius Bakke <mbakke@fastmail.com>
Cc: 30596@debbugs.gnu.org
Subject: [bug#30596] [PATCH 5/6] gnu: Add cmake@3.11.
Date: Sat, 03 Mar 2018 22:35:26 +0100 [thread overview]
Message-ID: <87h8pw971d.fsf@gnu.org> (raw)
In-Reply-To: <20180224190349.8155-5-mbakke@fastmail.com> (Marius Bakke's message of "Sat, 24 Feb 2018 20:03:48 +0100")
Marius Bakke <mbakke@fastmail.com> skribis:
> * gnu/packages/patches/cmake-3.11-pthread-fix.patch: New file.
> * gnu/local.mk (dist_patch_DATA): Register it.
> * gnu/packages/cmake.scm (cmake-3.11): New public variable.
[...]
> +;; Recent Ceph requires Boost 1.66, which in turn requires CMake 3.11 for
> +;; its updated "FindBoost.cmake" facility.
> +(define-public cmake-3.11
The actual upgrade is for ‘core-updates’ as well I guess?
> + (arguments
> + `(,@(substitute-keyword-arguments (package-arguments cmake)
> + ((#:phases phases)
Or simply:
(arguments
(substitute-keyword-arguments …))
Otherwise LGTM, thanks!
Ludo’.
next prev parent reply other threads:[~2018-03-03 21:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-24 19:01 [bug#30596] [PATCH 0/6] Update Ceph and dependencies Marius Bakke
2018-02-24 19:03 ` [bug#30596] [PATCH 1/6] gnu: rocksdb: Update to 5.10.3 Marius Bakke
2018-02-24 19:03 ` [bug#30596] [PATCH 2/6] gnu: snappy: Update to 1.1.7 Marius Bakke
2018-03-03 21:32 ` Ludovic Courtès
2018-02-24 19:03 ` [bug#30596] [PATCH 3/6] gnu: java-snappy: " Marius Bakke
2018-03-03 21:32 ` Ludovic Courtès
2018-02-24 19:03 ` [bug#30596] [PATCH 4/6] gnu: Add boost@1.66.0 Marius Bakke
2018-03-03 21:33 ` Ludovic Courtès
2018-02-24 19:03 ` [bug#30596] [PATCH 5/6] gnu: Add cmake@3.11 Marius Bakke
2018-03-03 21:35 ` Ludovic Courtès [this message]
2018-03-04 16:58 ` Marius Bakke
2018-02-24 19:03 ` [bug#30596] [PATCH 6/6] gnu: ceph: Update to 12.2.3 Marius Bakke
2018-03-03 21:37 ` Ludovic Courtès
2018-03-04 16:59 ` bug#30596: " Marius Bakke
2018-03-03 21:31 ` [bug#30596] [PATCH 1/6] gnu: rocksdb: Update to 5.10.3 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8pw971d.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30596@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
/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.