No problem for me to keep broken behavior of SolarisStudio.
Let me know when C++ Standard support including linking part is implemented, I
can help you to validate it on Solaris SPARC.
Thanks.
Marc
On 08/10/15 19:24, "cmake-developers on behalf of Brad King"
On 10/08/2015 11:38 AM, Brad King wrote:
> On 10/07/2015 03:22 PM, Stephen Kelly wrote:
>> The CMake 3.3 behavior of this is the same as it has always been since
>> introducing compile-features for SolarisStudio.
>
> Well that behavior was broken. We never had a nightly dashboard for it.
> Now
Brad King wrote:
> I don't want CMake to generate broken builds by default. We *know* it
> goes wrong on Solaris and cannot possibly work without user intervention.
Just some more on this:
The CMake 3.3 behavior of this is the same as it has always been since
introducing compile-features for
On 10/04/2015 10:47 AM, Stephen Kelly wrote:
> So, is this thread really about a bug, or is it a feature request?
I think it has become a feature request to select link flags for language
standard levels. It is conflated with a bug fix because the link flags
are needed to support existing
On Sun, Oct 04, 2015 at 16:47:40 +0200, Stephen Kelly wrote:
> The existing CMake feature deals with compilation, but does not deal with
> linking.
A generic target_link_options() is necessary for other things as well,
such as:
* -fsanitize=address needs to be passed to the linker to add
Brad King wrote:
> On 09/28/2015 03:20 PM, Brad King wrote:
>> for now we should look at turning off all language standard and
>> compile feature support for SolarisStudio when not hosted on Linux.
>
> Done here:
>
> Features: Disable support for Oracle SolarisStudio on non-Linux
>
On 09/28/2015 03:20 PM, Brad King wrote:
> for now we should look at turning off all language standard and
> compile feature support for SolarisStudio when not hosted on Linux.
Done here:
Features: Disable support for Oracle SolarisStudio on non-Linux
Seems OK for me… But my personal situation is even worst now! :)
The situation evolved from a buggy support of C++11 on Solaris to no support at
all. Do you have any idea (and schedule) for re-introduction of this feature,
knowing that the key point is the lack of propagating of c++11 compile
On Solaris, activating C++11 standard switch the compiler into a completely
different mode:
* Mangling is different
* C++ runtime is the GNU one, delivered as part of SolarisStudio 12.4 (Sun C++
runtime is no longer supported)
This is why the flag -std=c++11 must be passed to the link step to
Brad King wrote:
> On 09/28/2015 03:55 AM, CHEVRIER, Marc wrote:
>> Anyway, the main problem is the fact that, currently, C++ standard
>> handling is not usable on Solaris. Do have any plan to fix this problem
>> anytime soon?
>>
>> On 25/09/15 17:24, "Brad King" wrote:
>>> Compiling with a
On 09/28/2015 02:34 PM, Stephen Kelly wrote:
>> Steve? According to cmake-compile-features(7) you tested this with
>> Oracle SolarisStudio version 12.4.
>
> Yes, I tested it on SolarisStudio 12.4, but on linux (Ubuntu). Perhaps
> that's a relevant difference from 'real' Solaris.
That seems to
On 09/28/2015 03:55 AM, CHEVRIER, Marc wrote:
> Anyway, the main problem is the fact that, currently, C++ standard handling
> is not usable on Solaris. Do have any plan to fix this problem anytime soon?
>
> On 25/09/15 17:24, "Brad King" wrote:
>> Compiling with a -std= flag should link with such
Hi,
Bootstrapping CMake with the flags you specify and SOlarisStudio 12.4 enable to
generate a usable Cmake but some tests are failing with error related to CXX
standard.
For example, test 32, CompileFeatures generates error:
32: CMake Error: Error required internal CMake variable not set,
Steve,
On 09/25/2015 03:58 AM, CHEVRIER, Marc wrote:
> * If I add option -std=c++11 in the file .../Test.dir/link.txt,
> link is successful
Compiling with a -std= flag should link with such a flag too.
Flags like this are why CMake has always passed CMAKE_CXX_FLAGS
to the C++ compiler when
14 matches
Mail list logo
