From: Ricardo Wurmus <rekado@elephly.net>
To: 47972@debbugs.gnu.org
Subject: [bug#47972] Add irods.
Date: Fri, 23 Apr 2021 16:20:04 +0200 [thread overview]
Message-ID: <878s59qe0b.fsf@elephly.net> (raw)
Hi Guix,
this set of patches adds irods and irods-client-icommands. What
makes this patch set a little annoying is the fact that irods
insists on being built with clang 6; this means that we need
variants of existing GCC-built packages just so that they can be
linked with the irods libraries.
For the most part this is not too bad because we need specific
versions of certain libraries anyway. But for snappy-with-clang6
and avro-cpp it’s pretty bad. You’ll see that I’m using an inline
package definition for a variant of avro-cpp that is built with
clang; that package variant needs snappy, so I had to introduce
snappy-with-clang6.
Before we can actually merge this we would have to move this
avro-cpp variant to its own top-level package definition, because
it turns out that irods-client-icommands also needs it.
If you have an idea how to build irods with GCC, I’d be very
happy. (It takes quite some time to build irods, so be prepared
for long iteration cycles…)
--
Ricardo
next reply other threads:[~2021-04-23 14:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 14:20 Ricardo Wurmus [this message]
2021-04-23 14:31 ` [bug#47972] [PATCH 1/6] gnu: Add boost-for-irods Ricardo Wurmus
2021-04-23 14:31 ` [bug#47972] [PATCH 2/6] gnu: Add snappy-with-clang6 Ricardo Wurmus
2021-04-23 14:31 ` [bug#47972] [PATCH 3/6] gnu: Add nanodbc-for-irods Ricardo Wurmus
2021-04-23 14:31 ` [bug#47972] [PATCH 4/6] gnu: Add fmt-for-irods Ricardo Wurmus
2021-04-23 14:32 ` [bug#47972] [PATCH 5/6] gnu: Add irods Ricardo Wurmus
2021-04-23 14:32 ` [bug#47972] [PATCH 6/6] gnu: Add irods-client-icommands Ricardo Wurmus
2021-04-24 11:02 ` [bug#47972] [PATCH 1/6] gnu: Add boost-for-irods Maxime Devos
2021-06-10 8:28 ` [bug#47972] Add irods Ludovic Courtès
2021-06-14 14:48 ` bug#47972: " Ricardo Wurmus
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=878s59qe0b.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=47972@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).