From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: musl
Date: Mon, 26 Dec 2022 22:56:34 +0100 [thread overview]
Message-ID: <20221226215634.eb9lvQlM_M7AVtFf_b-FE5Rbfm5PEpVunrF_rd5AsA8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41295@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 338 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/41295#issuecomment-1365478315
Comment:
> Build failures on cross musl seem at least tangentially libssp related
Those aren't build failures they are broken packages that depend on musl. (Sometimes false positives can show up though)
next prev parent reply other threads:[~2022-12-26 21:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 6:05 [PR PATCH] musl CameronNemo
2022-12-26 15:45 ` musl JamiKettunen
2022-12-26 19:33 ` musl CameronNemo
2022-12-26 21:51 ` musl oreo639
2022-12-26 21:53 ` musl oreo639
2022-12-26 21:53 ` musl oreo639
2022-12-26 21:53 ` musl oreo639
2022-12-26 21:54 ` musl oreo639
2022-12-26 21:56 ` oreo639 [this message]
2022-12-27 17:22 ` musl dkwo
2022-12-27 17:33 ` musl CameronNemo
2022-12-27 17:36 ` musl nekopsykose
2022-12-27 17:39 ` musl paper42
2022-12-27 17:57 ` musl dkwo
2022-12-27 17:58 ` musl dkwo
2023-01-27 18:29 ` musl dkwo
2023-01-27 18:29 ` musl dkwo
2023-01-27 20:12 ` musl CameronNemo
2023-01-28 15:56 ` musl dkwo
2023-03-15 17:50 ` musl dkwo
2023-03-20 16:10 ` [PR PATCH] [Closed]: musl CameronNemo
2023-03-20 16:10 ` musl CameronNemo
2023-03-29 19:35 [PR PATCH] musl dkwo
2023-03-29 19:36 ` musl dkwo
2023-03-29 20:04 ` musl dkwo
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=20221226215634.eb9lvQlM_M7AVtFf_b-FE5Rbfm5PEpVunrF_rd5AsA8@z \
--to=oreo639@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).