Bug 1099282
| Summary: | clang doesn't understand -fstack-protector-strong | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Timothy St. Clair <tstclair> |
| Component: | llvm | Assignee: | Nobody's working on this, feel free to take it <nobody> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 23 | CC: | ajax, bos, dmalcolm, jv+fedora, pbrobinson, petersen, scottt.tw, tstclair |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-06-05 14:39:41 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 1
Timothy St. Clair
2014-05-20 02:43:19 UTC
Fedora's default CFLAGS assume gcc is the compiler, that's not about to change. Presumably clang needs to learn more command-line compatibility with gcc, and/or you need to filter that flag out of CFLAGS when you build. There appears to be a work-a-round, but I don't think it should fail out of the gate: https://lists.fedoraproject.org/pipermail/devel/2014-May/199477.html -------------------------- If you're building RPMs locally, you can drop your own definition of __global_cflags into '~/.rpmmacros': %__global_cflags -O2 -g ..etc.. If you are building a package that uses an autoconf-generated configure script, then simply setting CFLAGS before running configure should be enough, eg: CFLAGS="$( rpm --eval '%{__global_cflags}' | sed 's/-fstack-protector-strong//' )" \ ./configure -------------------------- Reassign to nobody@. I have no time and no interest in working on clang, and the only reason it's even in the llvm package is because it can't be built any other way. If anyone wishes to volunteer for comaintainer with a focus on clang, please let me know (preferably with direct email, if it's in bz I'll likely miss the request), I'll be happy to hook you up. This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23 -fstack-protector-strong was added in clang 3.8. It should work in Fedora 24 |