From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Cannot cross-compile libevent for armv5tel-musl
Date: Fri, 22 Jan 2021 21:52:10 +0100 [thread overview]
Message-ID: <20210122205210.ocNp3I23EdDLzG4cLj0pQdbBkL6ImGqhgypXfp11AlY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28103@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 912 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/28103#issuecomment-765676000
Comment:
okay, that should be updated now (will take a while to propagate since builders are still busy)
maybe we should just build libssp in all crosstoolchains, it'd make more sense perhaps... i mean you can just have libssp be installed through a makedepend, but considering it's a hard dependency of gcc package itself (and therefore always present in masterdir), it doesn't make much sense not to provide it through the crosstoolchain (things will generally not makedepend on libssp, though in practice nothing should really run into it, since glibc provides it builtin - on musl it's needed because we internally link to libssp_nonshared)
it's something to think about for next gcc update, right now it's not pressing at all, since it will practically never be a problem
next prev parent reply other threads:[~2021-01-22 20:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 16:51 [ISSUE] " lfdebrux
2021-01-22 17:12 ` pullmoll
2021-01-22 17:20 ` pullmoll
2021-01-22 17:22 ` pullmoll
2021-01-22 17:26 ` pullmoll
2021-01-22 19:49 ` Johnnynator
2021-01-22 20:11 ` pullmoll
2021-01-22 20:13 ` pullmoll
2021-01-22 20:30 ` q66
2021-01-22 20:34 ` q66
2021-01-22 20:48 ` q66
2021-01-22 20:52 ` q66 [this message]
2021-01-23 20:49 ` lfdebrux
2021-01-23 22:21 ` lfdebrux
2021-01-23 22:21 ` lfdebrux
2021-01-24 1:16 ` [ISSUE] [CLOSED] " q66
2022-02-17 5:11 ` RossComputerGuy
2022-03-26 3:27 ` Xlaits
2022-03-26 3:28 ` Xlaits
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=20210122205210.ocNp3I23EdDLzG4cLj0pQdbBkL6ImGqhgypXfp11AlY@z \
--to=q66@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).