Thanks Nate for the link. It does look promising, but I am using Boost 1.47.0 and I can't upgrade unfortunately. It looks like Locale was introduced in Boost 1.49.0. Is there a way to tell boost filesystem to not use locales and to treat all paths as UTF-8? Solaris paths are native UTF-8 and my customers will always pass in UTF-8 paths so there is no reason for them to be translated. Thanks, J On Wed, Sep 19, 2012 at 1:58 PM, Nathan Crookston wrote:

Hi,

On Wed, Sep 19, 2012 at 1:44 PM, JonathonS wrote:

...

Hi,

I am currently battling a buggy locale implementation (or lack thereof) in GCC on Solaris, which is affecting my use of boost::filesystem.

Please have a look at the following thread for more information regarding this: http://gcc.gnu.org/ml/gcc-help/2009-09/msg00212.html

In short, Solaris/GCC has a huge limitation that it does not support locales besides "C" or "POSIX". I talked to the GCC folks regarding this issue, and they said that at ONE time, GCC implemented the locale support for Solaris, but over time, the code was not maintained and therefore died :(

...

So, my question is whether anyone knows of a work-around for this?

I haven't tried it, but would using boost::locale in conjunction with filesystem work? Perhaps imbuing an ICU-backed locale would help, as shown in: http://www.boost.org/doc/libs/1_50_0/libs/locale/doc/html/default_encoding_u...

HTH, Nate _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

Thanks Lars for the help.

You could probably stub up a no-op codecvt and pass that in wherever Boost.Filesystem has an default codecvt parameter.

I thought of this idea, but unfortunately, this would require the devs to remember to pass in the stubbed codecvt implementation whenever they create a filesystem::path object. I guess I could create a helper function to return a path object, but then again, that would require them to use my helper function. I don't think they would like this. Is there a way to say, "always use this codecvt for all locales" ?

As I understand it, your explosions is due to the codecvt() instantiation itself, not the actual use of it.

Correct. Whenever boost filesystem gets instantiated, it tries to get the default locale via the invocation std::locale("") which seems to call the constructor for codecvt. If I was able to replace std::locale("") with std::locale(), then I think my problem would be solved because then this would force my customer's to set their locale via std::locale::global(...) and let them handle the issue :) Thanks, J