From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: libomp: update to 8.0.0.
Date: Thu, 09 May 2019 00:28:55 +0200 [thread overview]
Message-ID: <20190508222855.hJSCD98x-LaFQ_gZHL7jrC6z6S9fh-QIHiYzCEVKt4A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11546@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 703 bytes --]
New comment by atweiden on void-packages repository
https://github.com/void-linux/void-packages/pull/11546#issuecomment-490673636
Comment:
Upstream [notes](https://github.com/cryfs/cryfs/blob/develop/README.md#troubleshooting) not building against omp "will cause slower file system mount times". This was the impetus for adding the libomp package in the first place.
I think cryfs should be linking against libomp.
Maybe something is going wrong because I'm not including the full `-DOpenMP_CXX_FLAGS='-Xpreprocessor -fopenmp -I/path/to/openmp/include'` as recommend by upstream. IIRC, I left out the `-X` and `-f` opts there because of difficulty passing the whitespaced opts during the build.
next prev parent reply other threads:[~2019-05-08 22:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 22:51 [PR PATCH] [WIP] " voidlinux-github
2019-05-07 23:02 ` [PR PATCH] [Updated] " voidlinux-github
2019-05-07 23:02 ` voidlinux-github
2019-05-07 23:11 ` voidlinux-github
2019-05-07 23:11 ` voidlinux-github
2019-05-08 11:46 ` voidlinux-github
2019-05-08 21:46 ` voidlinux-github
2019-05-08 21:46 ` voidlinux-github
2019-05-08 22:05 ` voidlinux-github
2019-05-08 22:28 ` voidlinux-github [this message]
2019-05-09 13:04 ` voidlinux-github
2019-05-09 15:09 ` voidlinux-github
2019-05-09 15:09 ` voidlinux-github
2019-05-09 15:12 ` voidlinux-github
2019-05-09 15:13 ` voidlinux-github
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=20190508222855.hJSCD98x-LaFQ_gZHL7jrC6z6S9fh-QIHiYzCEVKt4A@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).