Re: [boost] Workaround for clang-linux + GNU stdlib + Boost.Iostreams

Subject: Re: [boost] Workaround for clang-linux + GNU stdlib + Boost.Iostreams
From: Bryce Lelbach (admin_at_[hidden])
Date: 2011-01-08 16:45:25

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Now that the clang-linux tester is back online, I realized this is a pretty
widespread issue.

A fix for this on x86 (32bit and 64bit) will be in Boost trunk.
<boost/detail/wint_t.hpp> and boost::wint_t should be used for maximum
portability. If not on clang + linux + gnu stdlib + x86, boost::wint_t is
typedef'd to std::wint_t (Boost.Config ensures std::wint_t is in the std
namespace).

On Mon, 03 Jan 2011 11:25:34 +0100
Mathias Gaunard <mathias.gaunard_at_[hidden]> wrote:

> On 01/01/2011 22:35, Bryce Lelbach wrote:
> > There's a discrepancy in the definition of wint_t between GCC and some later
> > versions of clang (clang defines it as an int, GCC an unsigned int). This
> > ends breaking Boost.Iostreams with a GNU GCC compiled version of the GNU
> > stdlib and clang (I'll restrain myself from giving the lengthy technical
> > explaination - if you have link-time errors with clang + GCC compiled
> > stdlib + Boost.Iostreams, this is probably the issue).
> 
> How about compiling libstdc++ with clang to avoid the discrepancy 
> altogether?
> 
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

> 

- -- 
Bryce Lelbach aka wash
boost-spirit.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAk0o2vUACgkQ9cB/V3/s9ExBswCfSehuSIMc/3yQoPcy5Vt9GTlf
IV4Anj65YwDTUBOkbxdE7NC972XHeLJo
=LWGz
-----END PGP SIGNATURE-----