From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: gc: Update to 8.2.2
Date: Fri, 02 Sep 2022 10:22:01 +0200 [thread overview]
Message-ID: <20220902082201.TvYytAyIcFDd_tQeKm3aobR42OCdmCw2GCRc5NSMhk0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39014@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
There's a merged pull request on the void-packages repository
gc: Update to 8.2.2
https://github.com/void-linux/void-packages/pull/39014
Description:
Other cleanups:
* Remove --enable-mmap (which is the default configure option now)
* No longer depends on libatomic_ops (provided the compiler is gcc or clang)
* Fix license (it is MIT, not GPL)
* Remove unneeded CFLAGS
* Set maintainer
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, (x64)
prev parent reply other threads:[~2022-09-02 8:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 21:33 [PR PATCH] " ivmai
2022-08-31 21:35 ` ivmai
2022-09-01 10:50 ` [PR PATCH] [Updated] " ivmai
2022-09-01 14:32 ` ivmai
2022-09-01 15:24 ` ivmai
2022-09-02 5:52 ` [PR PATCH] [Updated] " ivmai
2022-09-02 6:03 ` ivmai
2022-09-02 6:34 ` ivmai
2022-09-02 6:53 ` ivmai
2022-09-02 8:22 ` sgn [this message]
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=20220902082201.TvYytAyIcFDd_tQeKm3aobR42OCdmCw2GCRc5NSMhk0@z \
--to=sgn@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).