Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: memtest86+: fix musl build
Date: Sat, 24 Jun 2023 20:51:24 +0200	[thread overview]
Message-ID: <20230624185124.rZXpKQe5MOW8X2OM1LM1GAowEDx8ci-9RyHCURsSWBg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29562@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1382 bytes --]

There's a closed pull request on the void-packages repository

memtest86+: fix musl build
https://github.com/void-linux/void-packages/pull/29562

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?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR

<!--
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.)
- [x] I built this PR locally for my native architecture, x86_64-musl
- [x] I built this PR locally for these architectures:
  - [x] i686
  - [x] i686-musl
  - [x] x86_64


  parent reply	other threads:[~2023-06-24 18:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 10:50 [PR PATCH] memtest86+: fix cross build unspecd
2021-03-19 18:24 ` [PR REVIEW] " ericonr
2021-03-19 18:24 ` ericonr
2021-03-19 18:46 ` unspecd
2021-03-19 18:49 ` unspecd
2021-04-04 23:39 ` ericonr
2021-04-08  7:49 ` [PR PATCH] [Updated] " unspecd
2021-04-08  7:52 ` [PR REVIEW] " unspecd
2021-04-09  2:21 ` memtest86+: fix musl build ericonr
2021-04-14  3:40 ` unspecd
2023-06-24 18:51 ` classabbyamp [this message]
2023-06-24 18:51 ` classabbyamp

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=20230624185124.rZXpKQe5MOW8X2OM1LM1GAowEDx8ci-9RyHCURsSWBg@z \
    --to=classabbyamp@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).