The current version (0.15.1) of dev-games/ogre does not build. At first, it fails even to unpack successfully because of missing nvidia_cg toolkit on powerpc. After this is fixed, configure fails to properly detect gcc/g++ 4.x so that it defines HASH_EXT. Even after this is fixed, g++ build problems occur and emerge fails. Finally, a missing linux kernel header (on powerpc) makes the emerge fail once more. The supplied patch, fixes all these. Reproducible: Always Steps to Reproduce: 1. emerge ogre (on powerpc) Actual Results: The build fails to detect nvidia_cg toolkit (because it's not available on ppc). After this was fixed I encountered in sequence, configure, g++ build problems and missing linux kernel header files. After these were fixed, the problem was fixed. Expected Results: build and install. A patch is provided to fix all the problems. Even then though with the software emerging successfully, most(all?) of the Samples fail to run (though they build successfully) because most of the texture sample data is using the Nvidia Cg toolkit (.cg files which are written in the Cg language and not the GLSL language which would work). But that is not the problem of the package itself. It should work fine with code that uses GLSL, just not the samples.
Created attachment 134794 [details, diff] ebuild file patch PPC needs this patch to ebuild correctly and set the right configure options for the arch (and probably for all the arches as well).
Created attachment 134796 [details, diff] bootstrap patch bootstrap needs this patch to correctly detect recent versions of autoconf and automake
Created attachment 134800 [details, diff] fix compilation errors on gcc 4.x This patch fixes some compilation errors on g++ 4.x. Plus adds proper detection of gcc 4.x in configure.in
Created attachment 134801 [details, diff] ppc does not provide asm/io.h, asm/ioctl.h seems to work fine. Small patch to #include asm/ioctl.h instead of asm/io.h on ppc (where asm/io.h is not provided).
Thanks for your patches but is it really worth all of this effort to get a 3 year old release to work? Would it take as much to get 1.4.5 working?
OMG, I fixed the wrong version!! LOL Ok, I'll fix the newer version instead. OMG, what a blunder...
yep, not going to do any more stuff for 0.15.1
