[CMake] Assembler handling in 2.8.5 vs 2.8.4

[Alexander Neundorf]

On Monday 01 August 2011, Florian Reinhard wrote:
> 2011/7/29 Alexander Neundorf <a.neundorf-work at gmx.net>:
> > On Friday 29 July 2011, Florian Reinhard wrote:
> >> 2011/7/22 Alexander Neundorf <a.neundorf-work at gmx.net>:
> >> > Can you build cmake from this branch I just created ?
> >> > http://cmake.org/gitweb?p=stage/cmake.git;a=shortlog;h=refs/heads/TI_D
> >> > SP_ Compiler
> >> 
> >> Tested and failed:
> >> #cmake --version
> >> cmake version 2.8.5.20110722
> >> 
> >> #cmake -G"MinGW Makefiles" -DCMAKE_BUILD_TYPE=release ..
> >> -- Archiver: c:/tools/cgtools-7.2.4/bin/ar6x.exe
> >> -- The C compiler identification is TI_DSP
> >> -- The CXX compiler identification is TI_DSP
> >> -- Check for working C compiler: c:/tools/cgtools-7.2.4/bin/cl6x.exe
> >> terminate called after throwing an instance of 'std::logic_error'
> >>   what():  basic_string::_S_construct NULL not valid
> > 
> > Can you maybe run it in a debugger so we can get a backtrace ?
> 
> I attached the gdb output i got. I've been running gdb from a minGW32
> installation on a normal windows cmd.exe on windows7 x64.
> Unfortunately there's no backtrace (or i'm just don't know gdb well
> enough) and as soon as i execute "strace" after the cmake crash, gdb
> crashes as well.

Can you try to "catch throw" in gdb, then gdb should break when the exception 
is thrown, and you should be able to get a backtrace then, so we can see where 
it is thrown.

> >> Running on windows the output file extension is by default .exe which
> >> doesn't make sense, since there will be probably nobody compiling for
> >> the C6000 family on a C6000 system. So i guess having this would make
> >> sense:
> >> SET (CMAKE_EXECUTABLE_SUFFIX    .out)
> > 
> > This depends also on your target operating system. For which OS are you
> > developing ?
> 
> Actually none. 

Ok.

> I'm compiling a complete firmware for a Texas
> Instruments DSP (674x family) and no single binaries. 

Just to make sure I understand correctly: the firmware consists of one big 
binary which contains everything and there are no shared libraries or anything 
like this, right ?

Alex