I'm not quite sure what the problem is, since I've used TDM-GCC successfully (see my nightly builds which include the SFML examples). As for the posted code there are a few things that one doesn't/shouldn't do...
The default main functions usually looks like one of those and doesn't had uint32_t...
int main()
int main(int argc, char *argv[])
Since the return type is
int you should also return an integer rather than a boolean:
return 0;
Or just don't write any return statement, which is fine by the C++ standard , but just for the main function!
Third you shouldn't allocate a clock dynamically or you shouldn't manually manage memory at all. The posted code does at the moment leak memory, since you never call delete on the pointer.
If you need pointer like behavior then it's advised to use std::unique_ptr (or std::shared_ptr if the resource is shared) but in most cases it's possible to handle things on the stack rather than the heap.
Try the following code and check if you also get a SEG fault:
#include <SFML/System.hpp>
int main()
{
sf::Clock clock;
}
Also is there a specific reason why you use TDM-GCC? The official MinGW build have made an update recently and now ship with GCC 4.7.2.
