User forums > General (but related to Code::Blocks)
GCC 4.1.2 available (now relocatable!)
courage:
I try to build the samples of Ogre1.4 RC2, and it will throw a runtime error when starting to render graphics.
I think that maybe buinutils or mingw-runtime should be recompiled by configuring "--enable-fully-dynamic-string". :)
TDragon:
--- Quote from: courage on March 14, 2007, 02:19:43 pm ---I think that maybe buinutils or mingw-runtime should be recompiled by configuring "--enable-fully-dynamic-string". :)
--- End quote ---
Not a pertinent option for those packages; they have nothing to do with std::string objects.
Actually, I've been reading a bit further on using Ogre with MinGW and have come across this post on the Ogre forums, which suggests that GCC's exception handling can be another source of problems. Since I haven't actually built Ogre with GCC 4.1.2 (embarrassed cough), only 4.1.1, I will go ahead and do so and see if I can pin this error down.
Any details you can give me about your configuration, as well as the name of an Ogre sample which always throws the runtime error, would be appreciated as I work on this.
courage:
--- Quote from: TDragon on March 14, 2007, 02:28:39 pm ---Not a pertinent option for those packages; they have nothing to do with std::string objects.
--- End quote ---
Sorry for my ignorance and thanks for your work. :)
--- Quote from: TDragon on March 14, 2007, 02:28:39 pm ---Since I haven't actually built Ogre with GCC 4.1.2 (embarrassed cough), only 4.1.1, I will go ahead and do so and see if I can pin this error down.
--- End quote ---
Please don't be embarrassed.
I am appreciated your work. :)
--- Quote from: TDragon on March 14, 2007, 02:28:39 pm ---Any details you can give me about your configuration, as well as the name of an Ogre sample which always throws the runtime error, would be appreciated as I work on this.
--- End quote ---
I think I would find what the mistake I made. :o
I used the official prebuilt SDK and it could be compiled by gcc3.4.5.
I really feel so embarrassed. :?
TDragon:
--- Quote from: courage on March 14, 2007, 03:28:22 pm ---I think I would find what the mistake I made. :o
I used the official prebuilt SDK and it could be compiled by gcc3.4.5.
--- End quote ---
That is likely the source of the problem, although I wish it wasn't. Ideally, you should be able to use your own 4.1.2-compiled programs with the 3.4.5-compiled SDK.
I'm going to continue research in this area with both Ogre's official prebuilt SDK and my own build from sources. Further updates as results warrant.
wxLearner:
--- Quote from: courage on March 14, 2007, 03:28:22 pm ---I think I would find what the mistake I made. :o
I used the official prebuilt SDK and it could be compiled by gcc3.4.5.
I really feel embarrassed. :?
--- End quote ---
The problem seems to be, that the prebuilt SDK uses DWARF2 exception handling, but the default is SJLJ.
On windows there can appear problems with the superior DW2 EH, if functions that throw DW2 exceptions are used as callbacks by non-DW2-enabled functions (like Win32 API). I've read about this here. There is also information about the DW2 issue in this older thread.
Edit:
Sorry, it looks like SJLJ isn't the default EH mechanism. I don't know.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version