It is interesting, isn't it? The version which outputs warnings is the one that does compile successfully. At any rate, defining _WIN32 doesn't seem to alter anything: the executable generated by 0.9.26 generates the SIGILL when sqlite3_initialize() is called and has the bad ".stabst" section name, and the one generated by 0.9.25 runs to completion with correct ".stabstr" section.
On Tue, Aug 27, 2013 at 1:57 PM, Stephan Beal <[email protected]> wrote: > On Tue, Aug 27, 2013 at 6:43 PM, Tiago Rodrigues <[email protected]>wrote: > >> sqlite3.c:20250: warning: assignment makes pointer from integer without a >> cast >> sqlite3.c:44872: warning: assignment makes pointer from integer without a >> cast >> sqlite3.c:77174: warning: assignment makes pointer from integer without a >> cast >> > > In my experience that's normally caused by a using an implicitly-declared > function. > > Just out of curiosity: what happens if you add: -D_WIN32 to the compile > arguments?i know for a fact that sqlite3 builds just about anywhere, and > _suspect_ that it uses config vars not set by tcc. i just peeked at sqlite3 > and they use _WIN32 to figure out if they're on Windows. > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > http://gplus.to/sgbeal > > _______________________________________________ > Tinycc-devel mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/tinycc-devel > > -- In those days, in those distant days, in those nights, in those remote nights, in those years, in those distant years... - Gilgamesh, Enkidu and the Underworld
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
