[Vm-dev] Problem with sqWin32Backtrace.c

Igor Stasenko siguctua at gmail.com
Wed Mar 16 21:59:21 UTC 2011


On 16 March 2011 21:55, Levente Uzonyi <leves at elte.hu> wrote:
>
> On Wed, 16 Mar 2011, Igor Stasenko wrote:
>
>>
>> Hi, Eliot
>>
>> i don't get, why it barks with 'invalid storage class'?
>> Does this .c file has to be included into build, because it looks like
>> its can't be compiled by gcc, at least not in such form.
>> Maybe i again omit some #define ... and compiler trying to compile
>> different code.
>>
>>
>> c:/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c: In
>> function 'get_modules':
>> c:/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c:212:13:
>> error: invalid storage class for function 'find_in
>> _dll'
>> c:/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c:213:13:
>> error: invalid storage class for function 'find_in
>> _exe'
>> c:/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c:214:13:
>> error: invalid storage class for function 'find_in
>> _cog'
>> c:/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c:251:32:
>> error: 'find_in_dll' undeclared (first use in this
>> function)
>> c:/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c:251:32:
>> note: each undeclared identifier is reported only
>> once for each function it appears in
>> c:/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c:255:31:
>> error: 'find_in_exe' undeclared (first use in this
>> function)
>> c:/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c:261:41:
>> error: 'find_in_cog' undeclared (first use in this
>> function)
>> c:/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c: In
>> function 'find_in_dll':
>> c:/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c:290:13:
>> error: invalid storage class for function 'compute
>> _dll_symbols'
>> c:/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c: In
>> function 'find_in_exe':
>> c:/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c:320:13:
>> error: invalid storage class for function 'compute
>> _exe_symbols'
>> c:/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c: At top
>> level:
>> c:/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c:345:1:
>> warning: conflicting types for 'compute_exe_symbols
>> '
>> c:/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c:345:1:
>> error: static declaration of 'compute_exe_symbols'
>> follows non-static declaration
>> c:/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c:328:3:
>> note: previous implicit declaration of 'compute_exe
>> _symbols' was here
>> c:/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c:461:1:
>> warning: conflicting types for 'compute_dll_symbols
>> '
>> c:/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c:461:1:
>> error: static declaration of 'compute_dll_symbols'
>> follows non-static declaration
>> c:/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c:299:3:
>> note: previous implicit declaration of 'compute_dll
>> _symbols' was here
>> make[2]: ***
>> [CMakeFiles/Cog.dir/C_/projects/cog/sig-cog/platforms/win32/vm/sqWin32Backtrace.c.obj]
>> Error 1
>> make[1]: *** [CMakeFiles/Cog.dir/all] Error 2
>> make: *** [all] Error 2
>>
>>
>>
>> $ gcc -v
>> Using built-in specs.
>> COLLECT_GCC=C:\MinGW\bin\gcc.exe
>>
>> COLLECT_LTO_WRAPPER=c:/mingw/bin/../libexec/gcc/mingw32/4.5.2/lto-wrapper.exe
>> Target: mingw32
>> Configured with: ../gcc-4.5.2/configure
>> --enable-languages=c,c++,ada,fortran,objc,obj-c++
>> --disable-sjlj-exceptions --wi
>> th-dwarf2 --enable-shared --enable-libgomp --disable-win32-registry
>> --enable-libstdcxx-debug --enable-version-specific-r
>> untime-libs --disable-werror --build=mingw32 --prefix=/mingw
>> Thread model: win32
>> gcc version 4.5.2 (GCC)
>
> Your gcc is "too new", so some code has to be rewritten. It used to compile
> with 3.4.4.
>

Yeah. World is rolling, nobody sits on same place. Neither we should :)

>
> Levente
>
>>
>> --
>> Best regards,
>> Igor Stasenko AKA sig.
>>
>



-- 
Best regards,
Igor Stasenko AKA sig.


More information about the Vm-dev mailing list