ogre-1.4.1 is released. It's a maintenance release that should correct some of the existing bugs.
Using the 1.4.0 ebuild and cegui patch I get a linking error: .libs/OgreGLRenderSystem.o: In function `Ogre::GLRenderSystem::shutdown()': OgreGLRenderSystem.cpp:(.text+0x217b): undefined reference to `Ogre::HighLevelGp uProgramManager::removeFactory(Ogre::HighLevelGpuProgramFactory*)' collect2: ld returned 1 exit status libtool: install: error: relink `RenderSystem_GL.la' with the above command befo re installing it Not sure if this is related to the ebuild or just a bug in the code...
I could get it to build using the ogre 1.4.0 ebuild. No linking error here.
I'm using gcc-4.1.2, arch is x86_64. Ogre use flags: cegui cg examples freeimage gtk threads Cflags: -march=nocona -O3 -pipe Yours?
Renato. You are on amd64. I'm to. I get the same linking error here.. So it must be an amd64 problem. But there is not amd64 keyword so that makes sence.
Yes I suppose.. But 1.4.0 compiles fine under amd64. There was a problem with the library though (it seemed like it was with the Blue Highway font). I hoped that it would be corrected with 1.4.1, but it doesn't compile.. I'll try to find the source of the compilation problem. For now it should be running under 32bit, so it should be put in portage for that arch..
Please don't test just compilation as the freeimage issue is causing segfault to ANY app/demo/game/example in ogre.... http://www.ogre3d.org/phpBB2/viewtopic.php?p=222212#222212
The x86_64 compilation problem is caused by the ebuild/portage. It compiled fine by hand. Not sure what it was, but I suspect it had something to do with -march=nocona. I compared "by eye" the compilation command line for the GL render system and that was the only thing I've noticed to be different (apart from the g++/ x86_64-pc-linux-gnu-g++).. Will do more checks to see..
Created attachment 118866 [details] The differences between compilation commands Here's the difference between portage and "by hand" compilation commands for the GL render system library
It has nothing to do with -march=nocona. Now I suspect the culprit is the -lOgreMain directive, as this may link with the previous ogre installation library! This should not be happening I guess..
Ok, unmerging ogre 1.4.0 and emerging 1.4.1 works perfectly. Somehow something is getting confused by the existing ogre installation. This doesn't happen when compiling by hand (that is, with "./configure" and "make").
Created attachment 118996 [details] ogre-1.4.1.ebuild ebuild is just a copy of 1.4.0 with added `devil` USE flag. Works fine for me on two different machines. From the Changelog: * Allow Linux configure to choose to use DevIL again if wished, to avoid conflicts of FreeImage's modified image libraries & system libs.
No need for DevIL, the bug apparently doesn't affect gentoo users. After unmerging ogre-1.4.0, ogre-1.4.1 compiled and linked fine, and my program was able to compile and run perfectly using freeimage. So it's ok for the ~x86 and ~amd64 arches I suppose. But the linking problem when 1.4.0 is installed may need to be corrected..
thanks
