From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: C++ exceptions seem badly broken with aarch64-musl
Date: Fri, 28 Jun 2019 10:12:21 +0200 [thread overview]
Message-ID: <20190628081221.iAKzlTd9U_i3_S7d7wtt7uoQVa92oCn3xnRTKaAoUDY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-7498@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 451 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/7498#issuecomment-506645819
Comment:
`common/cross-profiles/aarch64.sh` has a comment for `XBPS_CFLAGS` which tells `# XXX not yet supported: -fstack-protector-strong` but our `gcc` template enables `--enable-default-ssp` and perhaps `gcc` decides to use the strong stack protection.
I don't know if the comment above still holds true, though.
next prev parent reply other threads:[~2019-06-28 8:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-7498@inbox.vuxu.org>
2019-06-28 2:57 ` voidlinux-github
2019-06-28 8:12 ` voidlinux-github [this message]
2019-06-29 23:43 ` voidlinux-github
2020-04-21 20:42 ` jnbr
2020-04-21 20:42 ` [ISSUE] [CLOSED] " jnbr
2020-10-12 21:52 ` jnbr
2020-10-12 21:52 ` jnbr
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=20190628081221.iAKzlTd9U_i3_S7d7wtt7uoQVa92oCn3xnRTKaAoUDY@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).