Summary: | dev-libs/libgcrypt-1.4.6 fails with the new -Ofast optimization level in gcc 4.6 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Xiangyan Sun <wishstudio> |
Component: | [OLD] GCC Porting | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | wishstudio |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 346809 | ||
Attachments: | Fix compilation. |
Description
Xiangyan Sun
2011-03-26 06:13:00 UTC
Created attachment 267227 [details, diff]
Fix compilation.
libgcrypt ebuild shouldnt be allowing flag munging in the first place The problem isn't necessarily Ofast, it's the fact that flag munging is making it into -O1fast. That is not a valid identifier. I've revbumped this to 1.4.6-r1 in CVS and removed the stupid flag munging. Please try that and confirm / reject -Ofast before I go and filter that as well. Closing as test requested. Please append whether or not this fixes the issue. The compilation problem resolved with dev-libs/libgcrypt-1.4.6-r1 and dev-libs/libgcrypt-1.5.0_beta1-r1. |