From: kruceter <kruceter@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] glslViewer: update to 3.0.7.
Date: Sat, 19 Nov 2022 02:00:42 +0100 [thread overview]
Message-ID: <20221119010042.1DdgJgCtks_DFMj7gT6V8tfVxQfjtCt9RWh2hUKN4zk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40547@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 439 bytes --]
New review comment by kruceter on void-packages repository
https://github.com/void-linux/void-packages/pull/40547#discussion_r1026996832
Comment:
Okay, false alarm. libatomic has to be placed under a condition.
`target_link_libraries(glslViewer PRIVATE atomic)` should not require libatomic on x86_64-musl since it already has one.
I have no idea, but before zapping masterdir for x86_64-musl it always complained about libatomic.
next prev parent reply other threads:[~2022-11-19 1:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 23:34 [PR PATCH] " kruceter
2022-11-18 12:24 ` [PR REVIEW] " paper42
2022-11-18 12:24 ` paper42
2022-11-18 12:24 ` paper42
2022-11-18 23:30 ` kruceter
2022-11-18 23:34 ` kruceter
2022-11-18 23:52 ` kruceter
2022-11-18 23:52 ` kruceter
2022-11-19 0:47 ` kruceter
2022-11-19 0:59 ` [PR PATCH] [Updated] " kruceter
2022-11-19 1:00 ` kruceter [this message]
2022-11-19 1:02 ` kruceter
2022-11-19 1:18 ` [PR REVIEW] " kruceter
2022-11-19 1:45 ` [PR PATCH] [Updated] " kruceter
2022-11-19 2:29 ` kruceter
2022-11-19 2:32 ` [PR REVIEW] " kruceter
2022-11-19 2:32 ` kruceter
2022-11-19 2:33 ` kruceter
2022-11-19 2:42 ` [PR PATCH] [Updated] " kruceter
2022-11-19 2:47 ` kruceter
2022-11-19 4:22 ` kruceter
2022-11-19 4:26 ` [PR REVIEW] " kruceter
2022-11-19 4:43 ` [PR PATCH] [Updated] " kruceter
2022-11-19 4:46 ` kruceter
2022-11-19 4:52 ` kruceter
2022-11-19 4:58 ` [PR REVIEW] " kruceter
2022-11-19 13:15 ` [PR PATCH] [Merged]: " paper42
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=20221119010042.1DdgJgCtks_DFMj7gT6V8tfVxQfjtCt9RWh2hUKN4zk@z \
--to=kruceter@users.noreply.github.com \
--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).