From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Kokkinizita
Date: Fri, 26 Feb 2021 05:59:04 +0100 [thread overview]
Message-ID: <20210226045904.Ak1c0qMwO5wHddXVAAxfD1EJMvk2ZbXxp9eYE9TRmSM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28809@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1761 bytes --]
There's a merged pull request on the void-packages repository
Kokkinizita
https://github.com/void-linux/void-packages/pull/28809
Description:
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
Setting CXXFLAGS in Makefile doesn't seem to work anymore since [void-packages#2325ae1](https://github.com/void-linux/void-packages/commit/2325ae153bd6011682782a6712f87338a9747ac7) so we need to set them in the template.
I've adapted them to those in the Makefile (e.g. `-ffast-math`) ~and enabled -march=native for non-cross builds~.
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
next prev parent reply other threads:[~2021-02-26 4:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 3:42 [PR PATCH] Kokkinizita [WIP] tibequadorian
2021-02-17 3:44 ` [PR PATCH] [Updated] " tibequadorian
2021-02-17 4:12 ` sgn
2021-02-17 4:43 ` tibequadorian
2021-02-17 7:56 ` Chocimier
2021-02-17 10:39 ` [PR PATCH] [Updated] " tibequadorian
2021-02-17 10:57 ` tibequadorian
2021-02-17 11:37 ` tibequadorian
2021-02-17 11:43 ` tibequadorian
2021-02-17 12:03 ` [PR PATCH] [Updated] " tibequadorian
2021-02-17 12:14 ` tibequadorian
2021-02-19 5:12 ` [PR REVIEW] Kokkinizita ericonr
2021-02-19 10:02 ` tibequadorian
2021-02-19 10:04 ` tibequadorian
2021-02-19 22:25 ` tibequadorian
2021-02-19 23:51 ` ericonr
2021-02-19 23:53 ` sgn
2021-02-20 0:03 ` ericonr
2021-02-20 0:56 ` tibequadorian
2021-02-24 4:16 ` ericonr
2021-02-25 8:48 ` [PR PATCH] [Updated] Kokkinizita tibequadorian
2021-02-25 8:50 ` [PR REVIEW] Kokkinizita tibequadorian
2021-02-25 8:51 ` [PR PATCH] [Updated] Kokkinizita tibequadorian
2021-02-25 8:59 ` Kokkinizita tibequadorian
2021-02-26 4:59 ` ericonr [this message]
2021-02-26 4:59 ` [PR REVIEW] Kokkinizita ericonr
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=20210226045904.Ak1c0qMwO5wHddXVAAxfD1EJMvk2ZbXxp9eYE9TRmSM@z \
--to=ericonr@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).