Guy Létourneau wrote:

I'm using Boost in an embedded environment (eCos). The processor architecture is Power PC. Since this target is not one of the "basic" targets supported by Boost, I had to skip the automatic configuration using bjam (I'm doing cross-compilation using Eclipse, and a custom version of gcc targeting eCos). I managed to have Boost work on my hardware but I'm getting a lot of warnings (> 200) when compiling my project. These warnings are all of the same type:

../boost_1_33_1/includeFiles/boost/aligned_storage.hpp warning: "BOOST_MSVC" is not defined

../boost_1_33_1/includeFiles/boost/archive/add_facet.hpp warning: "BOOST_DINKUMWARE_STDLIB" is not defined

../boost_1_33_1/includeFiles/boost/detail/call_traits.hpp warning: "__BORLANDC__" is not defined

../boost_1_33_1/includeFiles/boost/function.hpp warning: "__IBMCPP__" is not defined

And so forth. Because I didn't use bjam, all those prepro variables aren't defined. I'm using BOOST_NO_CONFIG in user.hpp as this setup seems to work fine in my environment (except for the warnings). Bottom line, I would like to know how to define those variables and/or what switch in the Boost config would be necessary so that my compiler stops complaining about them. It's probably an easy one for you Boost gurus but I still haven't found the correct way to solve that.

You should *not* be defining those: they are compiler specific defines, the only way to suppress those would be to change the warning level of your compiler: there should be an option in gcc to disable that warning. John.