From: ng0 <ng0@we.make.ritual.n0.is>
To: Marius Bakke <mbakke@fastmail.com>, guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add threadingbuildingblocks.
Date: Fri, 09 Sep 2016 09:16:23 +0000 [thread overview]
Message-ID: <87k2el302g.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <877falsyss.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me>
Marius Bakke <mbakke@fastmail.com> writes:
> ng0 <ng0@we.make.ritual.n0.is> writes:
>
>> + (arguments
>> + `(;; XXX: make 'check' is run with 'make all', however the 'all' phase takes
>> + ;; 30+ minutes on a AMD FX-4300 Quad-Core Processor buildmachine.
>> + #:tests? #f
>
> 30 minutes isn't bad, we have packages that takes longer. As long as it
> prints something to the console, it won't time out on slow machines
> either (but they will hopefully get substitutes from Hydra!).
I suspect it will be much longer, but I can enable it and let it run
today, see how much computing time it takes.
> The #:test-target seems to be 'test', by the way.
>
>> + (inputs
>> + `(("python" ,python)))
>
> Does it reference python at runtime, or is it only used for building?
runtime:
<DD>Build, install, and test Python* API for Intel TBB. See <A HREF="../python/index.html">details here</A>.
> You can check for references with `guix gc -R /gnu/store/<item>`.
>
>> Thanks, that's what I had at first. What about the product name, what is
>> it described as? Should I refer to debians description? I remember we
>> don't include © and ® in synopsis and description, but company name +
>> product works?
>
> I think I would phrase it as: "Threading Building Blocks (Intel TBB) is
> a C++ library for writing parallel programs that take full advantage of
> multicore performance."
Okay
> ~marius
>
--
ng0
For non-prism friendly talk find me on http://www.psyced.org
next prev parent reply other threads:[~2016-09-09 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 23:07 [PATCH] gnu: Add threadingbuildingblocks ng0
2016-09-08 23:11 ` ng0
2016-09-08 23:17 ` Jeff Mickey
2016-09-08 23:52 ` ng0
2016-09-09 0:26 ` Marius Bakke
2016-09-09 9:16 ` ng0 [this message]
2016-09-09 4:11 ` Eric Bavier
2016-09-09 9:17 ` ng0
2016-09-09 9:18 ` ng0
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=87k2el302g.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--cc=guix-devel@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 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).