Fails to build on Linux Mint (Debian)

Perkins

18-01-2011 21:19:59

I've been fighting with the compile process for python-ogre for a day and a half now, and I think it's time I ask for some help.

I followed version 4 of the compile guide: http://wiki.python-ogre.org/index.php/LinuxBuildV4, and everything went fine, mostly, at least up until it didn't (I don't remember where it broke, but I gave up on it). I realised the svn checkout I'd done was for non trunk code so I got the trunk code and tried again, it went even better this time, (I had to fix some path issues and it was importing some of the wrong headers (ones needed in windows) and other minor things like that, but all-in-all it worked well) until it was time to generate the code for ogre. By default it was downloading ogre-v1-7-0p1.tar.bz2, even though Environment.py is set for 1.7.2 for version. So I went and got ogre_src_v1-7-2.tar.bz2 and went from there. It died with almost exactly the same error as before.
Here is the out.log message.
http://barney.gonzaga.edu/~lperkins2/log.out
Unfortunately, it is 2.5 MiB or so, and pastebin cannot handle one of that size. It is 22606 lines long, but most of the middle is a big list of 'Functions that may not be accessable', the last section is actual error messages, they might be useful. I've included a number of them in a paste here: http://paste.pocoo.org/show/322898/
Any help on how to make it compile would be very much appreciated.

dermont

19-01-2011 16:59:56

I've been fighting with the compile process for python-ogre for a day and a half now, and I think it's time I ask for some help.

I followed version 4 of the compile guide: http://wiki.python-ogre.org/index.php/LinuxBuildV4, and everything went fine, mostly, at least up until it didn't (I don't remember where it broke, but I gave up on it). I realised the svn checkout I'd done was for non trunk code so I got the trunk code and tried again, it went even better this time, (I had to fix some path issues and it was importing some of the wrong headers (ones needed in windows) and other minor things like that, but all-in-all it worked well) until it was time to generate the code for ogre. By default it was downloading ogre-v1-7-0p1.tar.bz2, even though Environment.py is set for 1.7.2 for version. So I went and got ogre_src_v1-7-2.tar.bz2 and went from there. It died with almost exactly the same error as before.
Here is the out.log message.
http://barney.gonzaga.edu/~lperkins2/log.out
Unfortunately, it is 2.5 MiB or so, and pastebin cannot handle one of that size. It is 22606 lines long, but most of the middle is a big list of 'Functions that may not be accessable', the last section is actual error messages, they might be useful. I've included a number of them in a paste here: http://paste.pocoo.org/show/322898/
Any help on how to make it compile would be very much appreciated.


When you generate the code for the python-ogre it:

- first creates an xml cache in code_generators/cache/ogre_1.7.0_cache.xml
- uses the above cache to generate the code to generated/ogre_1.7.0
- Subsequent runs of generate_code will use the same cache.

The version "1.7.0" is defined in environment.py:

elif isLinux():
version = "1.7.0"


Normally after any updates to the code_generators one would delete ogre_1.7.0_cache.xml to re-generate the cache etc.
From your log the generate code appears to be output to generate/ogre_1.7.0, so I'm guessing that you are trying to generate the code from an old cache and encountering the same error.

If you update environment.py to 1.7.2 then you should have a fresh build for the python-ogre ogre module, i.e. code_generators/cacheogre_1.7.2_cache.xml and generated/ogre_1.7.2

elif isLinux():
#version = "1.7.0"
version = "1.7.2"


AFAIK 1.7.2 may not be officially supported yet on Linux; if you encounter more problems you can post here.

andy

21-01-2011 14:19:49

You might want to refresh from the SVN have another go based upon the wiki instructions..

I made a number of updates yesterday, bringing the Linux build back in line with Windows -- so far only tested Ogre and OIS modules which build cleanly...

Let us know if you have any issues and we'll get them sorted...

Andy