Supported compilers: gcc on osx?
Hi All, If I check the supported compilers page, gcc on darwin is supported - but I get the following error (boost_1_34_1/boost_1_35_0) * *The utf conversion in boost.program_options, for example to_utf8 gives std::runtime_error: locale::facet::_S_create_c_locale name not valid How do I repair this? The osx locale tools are not as conveniant as say ubuntu's ... (Should I not use Xcode's gcc, but build my own with a proper stdc++, or is there some fix in the os ?) Further: I have osx 10.5, but bjam thinks I have 10.4 - this is not a problem I guess, but it sure is not correct: bin/darwin/debug/link-static/macosx-version-10.4/threading-multi/ (the build path) Regards, - Dirk
On Tue, Apr 15, 2008 at 12:06 AM, Dirk Griffioen <dirk@code-shop.com> wrote:
Hi All,
If I check the supported compilers page, gcc on darwin is supported - but I get the following error (boost_1_34_1/boost_1_35_0) * *The utf conversion in boost.program_options, for example to_utf8 gives
std::runtime_error: locale::facet::_S_create_c_locale name not valid
How do I repair this? The osx locale tools are not as conveniant as say ubuntu's ... (Should I not use Xcode's gcc, but build my own with a proper stdc++, or is there some fix in the os ?)
Further: I have osx 10.5, but bjam thinks I have 10.4 - this is not a problem I guess, but it sure is not correct:
bin/darwin/debug/link-static/macosx-version-10.4/threading-multi/
I don't know much about the program options library or the OS X locale tools. But I can help a little with your questions about building under darwin. First of all, it is generally a good idea to stick with the gcc provided by Apple with the Xcode distribution. Even though the compiler is named gcc, you'll want to use the darwin toolset. It looks like this is what you've been doing. The toolset is not confused about what version of OS X your are running. The macosx-version-10.4 is indicating that 10.4 is the minimum version of OS X on which your built artifacts will run. At this point in time, it remains a good default. If you tell bjam to use macosx-version=10.5 you will be perhaps be abel to take advantage of 10.5-only features, but the resulting executables will not run under earlier OS versions. You can read more about this in Apple's documentation on the -mmacosx-version-min compiler option. See also the related -isysroot option. Hope this helps, Mat
Marcus - thanks for answering
I don't know much about the program options library or the OS X locale tools. But I can help a little with your questions about building under darwin.
Ok - hopefully someone knows (or I probably will have to digg deep :)
First of all, it is generally a good idea to stick with the gcc provided by Apple with the Xcode distribution. Even though the compiler is named gcc, you'll want to use the darwin toolset. It looks like this is what you've been doing. The toolset is not confused about what version of OS X your are running. The macosx-version-10.4 is indicating that 10.4 is the minimum version of OS X on which your built artifacts will run. At this point in time, it remains a good default. If you tell bjam to use macosx-version=10.5 you will be perhaps be abel to take advantage of 10.5-only features, but the resulting executables will not run under earlier OS versions. You can read more about this in Apple's documentation on the -mmacosx-version-min compiler option. See also the related -isysroot option.
Yes, I was building with --toolset=darwin; using macosx-version=10.5 leads to a 10.5 directory - thank you, I didn't know that :) Anyway, I tried it, but the 'locale::facet::_S_create_c_locale name not valid' is still there ...
Hope this helps, Mat _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- www.code-shop.com +31 6 411 92 024
participants (2)
-
Dirk Griffioen -
Mat Marcus