On Fri, Feb 19, 2016 at 5:46 PM, Magnus Ihse Bursie <[email protected]> wrote: > On 2016-02-19 09:40, Volker Simonis wrote: >> >> On Thu, Feb 18, 2016 at 9:45 PM, Magnus Ihse Bursie >> <[email protected]> wrote: >>> >>> On 2016-02-18 11:17, Volker Simonis wrote: >>>> >>>> Thanks. >>>> >>>> Unfortunately, --disable-warnings-as-errors doesn't help in this case. >>>> If we want to still make it possible to build with 12u3 we have to >>>> filter out the corresponding -erroff options depending on the compiler >>>> version. >>> >>> Due to reasons like this, we would like to support a minimal span of >>> versions for the solstudio compiler. So if you are alright with upgrading >>> to >>> 12u4, we'd prefer to drop support for 12u3 completely. Filtering out >>> error >>> options like this is quite a pain, otherwise. >>> >>> I believe there are few community users that care much about Solaris and >>> solstudio. Had you not told me you were building on Solaris, I would have >>> guessed only Oracle did so. This gives us, I believe, a better chance at >>> enforcing stricter restrictions on the set of supported versions, >>> compared >>> to the situation for e.g. gcc and linux. >>> >> For our product builds we will most probably have to stay with older >> version for a couple of reasons (building on older OS release, >> dependency on other products/libraries, licensing/support issues, >> etc). But as long as the problem is just a few unknown compiler >> options I'm fine if you say you don't want to support them any more >> (we can easily remove them in our proprietary build). >> >> This assessment would of course change if it would be necessary to >> make bigger source code changes (i.e. template code) in order to >> support older compilers. But fortunately we're not there until now :) >> >> By the way, do you know if the upcoming "HotSpot C++ Unit-Test >> Framework" (JEP 281) will impose further restrictions on the supported >> C++ compilers? > > > Not that I know of, no. But perhaps no-one have ever tried compiling GTest > on xlc, so you might have some porting work to do if you want to be able to > use the unit test framework. >
Yet another adventure we have to survive :) > /Magnus > > >> >> Regards, >> Volker >> >
