Michael Marcin wrote:

"Michael Marcin" wrote in message news:ee7ljj$9o4$1@sea.gmane.org...

...

Using WinARM version 20060606 (gcc 4.1.1) compiling with -fno-rtti gives: 1>..\..\sdk\boost\inc/boost/detail/sp_counted_impl.hpp: In member function 'virtual void* boost::detail::sp_counted_impl_pd::get_deleter(const std::type_info&)': 1>..\..\sdk\boost\inc/boost/detail/sp_counted_impl.hpp(150): error: cannot use typeid with -fno-rtti 1>..\..\sdk\boost\inc/boost/detail/sp_counted_impl.hpp: In member function 'virtual void* boost::detail::sp_counted_impl_pda

...

...

...

get_deleter(const std::type_info&)': 1>..\..\sdk\boost\inc/boost/detail/sp_counted_impl.hpp(220): error: cannot use typeid with -fno-rtti 1>..\..\sdk\boost\inc/boost/shared_ptr.hpp: In function 'D* boost::get_deleter(const boost::shared_ptr<U>&)': 1>..\..\sdk\boost\inc/boost/shared_ptr.hpp(540): error: cannot use typeid with -fno-rtti

I thought typeid can work at compile-time without rtti (seems to for msvc8) but I guess not.

Any ideas?

So I take it there is no flags for gcc to enable compile-time rtti only and there are no other ways around the typeid error in shared_ptr's implementation.

If you don't need to use get_deleter, just patch your local copy to 'return 0' from the three functions.

Michael Marcin wrote:

"Peter Dimov" wrote in message news:003201c6d83e$80bf9910$6507a8c0@pdimov2...

...

Michael Marcin wrote:

...

"Michael Marcin" wrote in message news:ee7ljj$9o4$1@sea.gmane.org...

...

Using WinARM version 20060606 (gcc 4.1.1) compiling with -fno-rtti

I thought typeid can work at compile-time without rtti (seems to for msvc8) but I guess not.

Any ideas?

So I take it there is no flags for gcc to enable compile-time rtti only and there are no other ways around the typeid error in shared_ptr's implementation.

If you don't need to use get_deleter, just patch your local copy to 'return 0' from the three functions.

Fair enough I suppose.

I see that I already have a request for a BOOST_SP_DISABLE_GET_DELETER macro for this reason, but the earliest it can surface in an official release is 1.35, so the above is your best bet today. :-)