From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Revert "build-style/void-cross: always enable libssp"
Date: Mon, 26 Dec 2022 10:37:20 +0100 [thread overview]
Message-ID: <20221226093720.EckyEIdnIzNGxk-KM5nnR4eIuj9RJCO6sZZ6vUhk4LE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41229@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/41229#issuecomment-1364889593
Comment:
Not that I am aware of.
libssp.so will still be provided by the libssp package and libssp.so was never added to cross-vpkg-dummy so it shouldn't break anything that wasn't already broken (packages depending on libssp should still pull in the libssp package iirc).
If there is something I missed please let me know.
The other gcc PR (#41294) will definitely need testing to make sure that the arm/aarch64 packages still compile fine and to make sure I didn't miss anything.
next prev parent reply other threads:[~2022-12-26 9:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 23:21 [PR PATCH] " oreo639
2022-12-22 1:33 ` [PR PATCH] [Updated] " oreo639
2022-12-26 4:03 ` CameronNemo
2022-12-26 5:03 ` oreo639
2022-12-26 5:04 ` oreo639
2022-12-26 5:04 ` oreo639
2022-12-26 5:05 ` oreo639
2022-12-26 5:06 ` oreo639
2022-12-26 5:19 ` oreo639
2022-12-26 7:46 ` oreo639
2022-12-26 9:37 ` oreo639 [this message]
2022-12-27 10:21 ` [PR PATCH] [Updated] " oreo639
2022-12-27 10:21 ` Drop libssp from cross compilers oreo639
2022-12-27 10:27 ` [PR PATCH] [Updated] " oreo639
2022-12-27 10:35 ` oreo639
2022-12-27 10:55 ` oreo639
2022-12-27 10:56 ` oreo639
2022-12-27 12:14 ` [PR PATCH] [Updated] " oreo639
2023-01-09 8:32 ` oreo639
2023-01-09 12:14 ` oreo639
2023-01-20 7:45 ` [PR PATCH] [Closed]: " sgn
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=20221226093720.EckyEIdnIzNGxk-KM5nnR4eIuj9RJCO6sZZ6vUhk4LE@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).