Summary: | devel/psptoolchain-newlib: fix to recent change that made library unusable | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Tassilo Philipp <tphilipp> | ||||
Component: | Individual Port(s) | Assignee: | Steve Wills <swills> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Some People | ||||||
Priority: | --- | ||||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Tassilo Philipp
2019-06-05 16:30:10 UTC
Sorry, I didn't dig deep enough, so correction: the problem actually already happened when SSP_CFLAGS was added, the commit mentioned merely kept the port building. That said, the patch is still working and fixes the use of the library, as described. However, I'm wondering if using WITHOUT_SSP would be better? I lean towards the patch, as-is, to explicitly disabe the stack guards. A commit references this bug: Author: swills Date: Sat Jun 8 00:23:43 UTC 2019 New revision: 503680 URL: https://svnweb.freebsd.org/changeset/ports/503680 Log: devel/psptoolchain-newlib: fix to recent change that made library unusable PR: 238341 Submitted by: Tassilo Philipp <tphilipp@potion-studios.com> (maintainer) Changes: head/devel/psptoolchain-newlib/Makefile Committed, slightly modified so it's more explicit. Thanks! Thanks! I think you wanted to remove the SSP_CFLAGS?= line, though, as you did with PR 238342? |