[Pkg-qof-maintainers] Bug#672085: qof: ftbfs with GCC-4.7
Matthias Klose
doko at debian.org
Tue May 8 22:26:25 UTC 2012
On 08.05.2012 22:21, Neil Williams wrote:
> tag 672085 + help quit
>
> On Tue, 08 May 2012 18:57:52 +0000 Matthias Klose <doko at debian.org> wrote:
>
>> user debian-gcc at lists.debian.org usertags 672085 + ftbfs-gcc-4.7 thanks
>>
>> The build failure is exposed by building with gcc-4.7/g++-4.7, which is
>> now the default gcc/g++ on x86 architectures.
>>
>> Some hints on fixing these issues can be found at
>> http://gcc.gnu.org/gcc-4.7/porting_to.html
>
> This particular issue isn't covered in those hints, it's an internal MD5
> process which is the same as the internal MD5 code in eglibc.
>
> I could hide the problem by dropping -Werror or adding -fno-strict-aliasing
> but it's not clear to me why the same code compiles in eglibc and not in
> qof, especially when eglibc is passing -fstrict-aliasing.
eglibc doesn't use the default compiler, but the warning is still seen when
building a recent libiberty (e.g. in gcc-4.7, or gcc-snapshot).
forwarded to http://gcc.gnu.org/PR53285 for now.
More information about the Pkg-qof-maintainers
mailing list