| Summary: | app-crypt/gpgme-1.8.0-r3 fails to build with GCC 4.9 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | René Rhéaume <rene.rheaume> |
| Component: | Current packages | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | alonbl |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | gpgme-1.8.0-gcc-4.patch | ||
This is unlikely to get accepted upstream, which will be the prerequisite for adding this patch to the ebuild. I can only recommend to make the upgrade to latest stable GCC sooner than later. @crypto, should the ebuild check for min active gcc version instead? Please attach your build.log and emerge --info. (In reply to Andreas Sturmlechner from comment #1) > @crypto, should the ebuild check for min active gcc version instead? I would consider that if it was a new compiler or even recent one... However, I do not see any reason to tweak ebuild that far into the past. Please communicate with upstream. |
Created attachment 499540 [details, diff] gpgme-1.8.0-gcc-4.patch GpgME fails to build with GCC 4.9.x because of a few missing C++11 features in libstdc++ . Instead of using these features, we call their C equivalent.