Debian Bug report logs - #642916
Combination of -std=gnu++0x and -fno-rtti fails to build

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Max Kellermann <max@duempel.org>

To: submit@bugs.debian.org

Subject: Combination of -std=gnu++0x and -fno-rtti fails to build

Date: Sun, 25 Sep 2011 18:15:00 +0200

Package: gcc-mingw32
Version: 4.4.4-1

$ echo '#include <memory>' |i586-mingw32msvc-gcc -x c++ -fno-rtti -std=gnu++0x -
In file included from /usr/lib/gcc/i586-mingw32msvc/4.4.4/include/c++/memory:83,
                 from <stdin>:1:
/usr/lib/gcc/i586-mingw32msvc/4.4.4/include/c++/bits/shared_ptr.h: In member function 'virtual void* std::_Sp_counted_deleter<_Ptr, _Deleter, _Alloc, _Lp>::_M_get_deleter(const std::type_info&)':
/usr/lib/gcc/i586-mingw32msvc/4.4.4/include/c++/bits/shared_ptr.h:146: error: cannot use typeid with -fno-rtti
/usr/lib/gcc/i586-mingw32msvc/4.4.4/include/c++/bits/shared_ptr.h: In member function 'virtual void* std::_Sp_counted_ptr_inplace<_Tp, _Alloc, _Lp>::_M_get_deleter(const std::type_info&)':
/usr/lib/gcc/i586-mingw32msvc/4.4.4/include/c++/bits/shared_ptr.h:204: error: cannot use typeid with -fno-rtti
/usr/lib/gcc/i586-mingw32msvc/4.4.4/include/c++/bits/shared_ptr.h: In constructor 'std::__shared_ptr<_Tp, _Lp>::__shared_ptr(std::_Sp_make_shared_tag, _Alloc, _Args&& ...)':
/usr/lib/gcc/i586-mingw32msvc/4.4.4/include/c++/bits/shared_ptr.h:861: error: cannot use typeid with -fno-rtti
/usr/lib/gcc/i586-mingw32msvc/4.4.4/include/c++/bits/shared_ptr.h: In function '_Del* std::get_deleter(const std::__shared_ptr<_Tp2, _Lp>&)':
/usr/lib/gcc/i586-mingw32msvc/4.4.4/include/c++/bits/shared_ptr.h:1005: error: cannot use typeid with -fno-rtti

Message #10 received at 642916@bugs.debian.org (full text, mbox, reply):

From: Stephen Kitt <steve@sk2.org>

To: Max Kellermann <max@duempel.org>, 642916@bugs.debian.org

Subject: Re: Bug#642916: Combination of -std=gnu++0x and -fno-rtti fails to build

Date: Sun, 25 Sep 2011 23:47:34 +0200

Hi,

Thanks for taking the time to report this bug.

On Sun, Sep 25, 2011 at 06:15:00PM +0200, Max Kellermann wrote:
> $ echo '#include <memory>' |i586-mingw32msvc-gcc -x c++ -fno-rtti -std=gnu++0x -
> In file included from /usr/lib/gcc/i586-mingw32msvc/4.4.4/include/c++/memory:83,
>                  from <stdin>:1:
[...]

I've found traces of similar bugs in gcc 4.4.4, for example
https://bugzilla.mozilla.org/show_bug.cgi?id=654493 - this doesn't
seem specific to gcc-mingw32. In fact g++-4.4 in Debian (4.4.6) still
has the same bug!

gcc-mingw32 is now in simple maintenance mode, and I intend to have it
removed once all its reverse build-dependencies have switched to
gcc-mingw-w64 (which can build 32-bit executables and DLLs). Would it
be possible for you to give gcc-mingw-w64 a try?

Regards,

Stephen

Message #15 received at 642916@bugs.debian.org (full text, mbox, reply):

From: Max Kellermann <max@duempel.org>

To: Stephen Kitt <steve@sk2.org>

Cc: 642916@bugs.debian.org

Subject: Re: Bug#642916: Combination of -std=gnu++0x and -fno-rtti fails to build

Date: Mon, 26 Sep 2011 07:04:06 +0200

On 2011/09/25 23:47, Stephen Kitt <steve@sk2.org> wrote:
> I've found traces of similar bugs in gcc 4.4.4, for example
> https://bugzilla.mozilla.org/show_bug.cgi?id=654493 - this doesn't
> seem specific to gcc-mingw32. In fact g++-4.4 in Debian (4.4.6) still
> has the same bug!

That's right - the bug is in gcc4.4's libstdc++.  Seems to be fixed
from 4.5 on.  With mingw32, I seemed to be stuck with the old gcc4.4.

> gcc-mingw32 is now in simple maintenance mode, and I intend to have it
> removed once all its reverse build-dependencies have switched to
> gcc-mingw-w64 (which can build 32-bit executables and DLLs). Would it
> be possible for you to give gcc-mingw-w64 a try?

The bug does not occur here (it's gcc 4.6).  The binaries have
confusing names, though: "i686-w64-..." is unable to generate 64 bit
binaries, despite the "w64" name part.

If gcc-mingw-w64 is the designated full-featured successor of
gcc-mingw32, we can close this bug.

Message #20 received at 642916-done@bugs.debian.org (full text, mbox, reply):

From: Stephen Kitt <steve@sk2.org>

To: Max Kellermann <max@duempel.org>

Cc: 642916-done@bugs.debian.org

Subject: Re: Bug#642916: Combination of -std=gnu++0x and -fno-rtti fails to build

Date: Mon, 26 Sep 2011 07:14:06 +0200

Hi Max,

On Mon, Sep 26, 2011 at 07:04:06AM +0200, Max Kellermann wrote:
> On 2011/09/25 23:47, Stephen Kitt <steve@sk2.org> wrote:
> > gcc-mingw32 is now in simple maintenance mode, and I intend to have it
> > removed once all its reverse build-dependencies have switched to
> > gcc-mingw-w64 (which can build 32-bit executables and DLLs). Would it
> > be possible for you to give gcc-mingw-w64 a try?
> 
> The bug does not occur here (it's gcc 4.6).  The binaries have
> confusing names, though: "i686-w64-..." is unable to generate 64 bit
> binaries, despite the "w64" name part.

Yes, they are somewhat confusing, but that's what's used upstream and
in other distributions; see http://bugs.debian.org/622276 for a
detailed explanation.

> If gcc-mingw-w64 is the designated full-featured successor of
> gcc-mingw32, we can close this bug.

OK, done!

Thanks,

Stephen

Send a report that this bug log contains spam.