Description of problem:
gcc-4.7.0 fixes a bug that various packages rely on
Version-Release number of selected component (if applicable):
4.7.0
How reproducible:
100% deterministic.
Steps to Reproduce: 1. Try to build a package such as Crypto++ v5.6.1 with a pre-release of gcc 4.7.0. 2. 3.
Actual results:
Compile failure.
Expected results:
Compile success.
Additional info:
As reported by Jakub Jellinek: http://lists.fedoraproject.org/pipermail/devel/2011-December/160723.html As tracked on launchpad: https://bugs.launchpad.net/gcc/+bug/915018, which has links to the issue trackers for Crypto++ and pycryptopp.
Description of problem:
gcc-4.7.0 fixes a bug that various packages rely on
Version-Release number of selected component (if applicable):
4.7.0
How reproducible:
100% deterministic.
Steps to Reproduce:
1. Try to build a package such as Crypto++ v5.6.1 with a pre-release of gcc 4.7.0.
2.
3.
Actual results:
Compile failure.
Expected results:
Compile success.
Additional info:
As reported by Jakub Jellinek: http:// lists.fedorapro ject.org/ pipermail/ devel/2011- December/ 160723. html /bugs.launchpad .net/gcc/ +bug/915018, which has links to the issue trackers for Crypto++ and pycryptopp.
As tracked on launchpad: https:/