From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [WIP] boost: update to 1.72.0.
Date: Thu, 09 Jan 2020 19:40:36 +0100 [thread overview]
Message-ID: <20200109184036.4lcrbRdQ6DQJjAxSn2H8VmG0iW9ycLwIhEEZAXANdzo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18135@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/pull/18135#issuecomment-572695507
Comment:
> also i think `threading=multi` is actually not default and we've been building boost wrong all along
Why that? I think multi is what we want. Since threadsafe code should work everywhere albeit with a performance drawback. The alternative would be to just build boost 4 times instead of only 2 times right now (`static/single`, `static/multi`, `dynamic/single`, `dynamic/multi`), but I doubt that it would be worth it.
> threading
>
> Allowed values: single, multi
>
> Controls if the project should be built in multi-threaded mode. This feature does not necessary change code generation in the compiler, but it causes the compiler to link to additional or different runtime libraries, and define additional preprocessor symbols (for example, _MT on Windows and _REENTRANT on Linux). How those symbols affect the compiled code depends on the code itself.
next prev parent reply other threads:[~2020-01-09 18:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 12:33 [PR PATCH] " voidlinux-github
2020-01-09 12:35 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-09 12:36 ` voidlinux-github
2020-01-09 15:49 ` [WIP] " voidlinux-github
2020-01-09 15:52 ` voidlinux-github
2020-01-09 17:14 ` voidlinux-github
2020-01-09 18:40 ` voidlinux-github [this message]
2020-01-09 18:43 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-09 19:00 ` voidlinux-github
2020-01-09 19:01 ` voidlinux-github
2020-01-09 19:17 ` voidlinux-github
2020-01-09 19:42 ` voidlinux-github
2020-01-11 0:13 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-22 20:34 ` voidlinux-github
2020-01-25 18:08 ` voidlinux-github
2020-01-25 20:18 ` voidlinux-github
2020-01-31 6:02 ` [PR PATCH] [Closed]: " voidlinux-github
2020-01-31 6:02 ` 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=20200109184036.4lcrbRdQ6DQJjAxSn2H8VmG0iW9ycLwIhEEZAXANdzo@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).