Problems compiling under 64-bit Linux?

[Olav]

I am trying to get Python-Ogre installed on my Ubuntu 64-bit (Intrepid
Ibex). The .debs I found here (http://wiki.python-ogre.org/index.php/
LinuxBuildV2) was for Hardy and Gutsy and didn't work (Will there be
Ibex-debs anytime soon?). I managed to compile Ogre and run the
example files (Step 4), but on step 5 I keep getting errors.

Are there known problems with Python-Ogre+64-bit Linux?

[Matej Mo]

Hi!

I was able to compile python-oge on Ubuntu 64 Interpid (just today),
BUT I was unable to run it. When I try to run any demo (or custom
code) I get a blank screen (after the configuration dialog) and
there's a big memory leak until the system comes to a crawl after a
few seconds. The log output always stops at this line: "Parsing
scripts for resource group Autodetect". I've been able to successfully
compile and run python-ogre on other 32 bit distros.

What compile errors do you get?

[Olav]

This is what I get in the terminal:

$ python python-ogre/BuildModule.py -g -c ogre ois cegui
PythonOgre.BuildModule: INFO Building Source code for ogre
PythonOgre.BuildModule: WARNING Task Failed
PythonOgre.BuildModule: INFO Compiling Source code for ogre
PythonOgre.BuildModule: WARNING Task Failed
PythonOgre.BuildModule: INFO Building Source code for ois
PythonOgre.BuildModule: WARNING Task Failed
PythonOgre.BuildModule: INFO Compiling Source code for ois
PythonOgre.BuildModule: WARNING Task Failed
PythonOgre.BuildModule: INFO Building Source code for cegui
PythonOgre.BuildModule: WARNING Task Failed
PythonOgre.BuildModule: INFO Compiling Source code for cegui
PythonOgre.BuildModule: WARNING Task Failed

This is my out.log: http://pastebin.com/mcd1e9f8

All help is appreciated.

[Matej Mo]

> ImportError: No module named pyplusplus

I think I had the same problem the first time I tried to compile
python-ogre (there were a lot off problems, so I dont remember
correctly :))

You can solve this by installing py++ in the system location (/usr/lib/
python2.5/site-packages)
Go to the directory '/home/olav/sources/pyplusplus' and issue: 'sudo
python setup.py install'
After this the compiler should find the modules

[Roman Yakovenko]

On Tue, Jan 27, 2009 at 11:18 PM, Olav <olal...@gmail.com> wrote:
>
> This is what I get in the terminal:
>
> $ python python-ogre/BuildModule.py -g -c ogre ois cegui
> PythonOgre.BuildModule: INFO Building Source code for ogre
> PythonOgre.BuildModule: WARNING Task Failed
> PythonOgre.BuildModule: INFO Compiling Source code for ogre
> PythonOgre.BuildModule: WARNING Task Failed
> PythonOgre.BuildModule: INFO Building Source code for ois
> PythonOgre.BuildModule: WARNING Task Failed
> PythonOgre.BuildModule: INFO Compiling Source code for ois
> PythonOgre.BuildModule: WARNING Task Failed
> PythonOgre.BuildModule: INFO Building Source code for cegui
> PythonOgre.BuildModule: WARNING Task Failed
> PythonOgre.BuildModule: INFO Compiling Source code for cegui
> PythonOgre.BuildModule: WARNING Task Failed
>
> This is my out.log: http://pastebin.com/mcd1e9f8

It looks like you don't have Py++ ( pyplusplus ) installed, am I right?
If so, you need to install pygccxml and Py++.

P.S. I don't know the exact revision used and whether the build
scripts should install the packages.

--
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/

[Andy Miller]

You have to get Ogre to build first before anything else will work so do a 

python python-ogre/BuildModule.py -g ogre

Then look at log.out to see what happened...

Also ensure you do an svn up before trying as I've made major changes over the last 2 days in anticipation of branching a stable 1.6.1 version...

Thanks

Andy

2009/1/28 Roman Yakovenko <roman.y...@gmail.com>

[Andy Miller]

Sorry -- didn't see the link to your log.out...  Can you try the following....

python python-ogre/BuildModule -r pyplusplus pygccxml

python python-ogre/BuildModule -b pyplusplus pygccxml

And let me know what goes wrong...

Andy

2009/1/28 Andy Miller <nzmi...@gmail.com>

[Olav]

I have installed pygccxml and pyplusplus now, but It still doesn't
work. I''ve downloaded the latest revision of Python-Ogre today.

Here's my out.log: http://pastebin.com/m29cc5267

For some reason Boost always fail when I try to compile it. What can I
do?

On 27 Jan, 23:36, Andy Miller <nzmill...@gmail.com> wrote:
> Sorry -- didn't see the link to your log.out...  Can you try the
> following....
> python python-ogre/BuildModule -r pyplusplus pygccxml
> python python-ogre/BuildModule -b pyplusplus pygccxml
>
> And let me know what goes wrong...
>
> Andy
>

> 2009/1/28 Andy Miller <nzmill...@gmail.com>

>
> > You have to get Ogre to build first before anything else will work so do a
> > python python-ogre/BuildModule.py -g ogre
>
> > Then look at log.out to see what happened...
>
> > Also ensure you do an svn up before trying as I've made major changes over
> > the last 2 days in anticipation of branching a stable 1.6.1 version...
>
> > Thanks
> > Andy
>

> > 2009/1/28 Roman Yakovenko <roman.yakove...@gmail.com>

[Matej Mo]

I encountered the same problem and just copied everything from
'working_dir/boost_1_37/boost/' to 'working_dir/root/usr/include/
boost_1_37/boost/'
Afterwards it compiled without problems.

I'm really interested if you will be able to run the demos after the
compilation. Waiting to hear from you..

[Olav]

Thanks, Matej. I'm one stem closer. I ran

python python-ogre/BuildModule.py -g ogre

And it seemed to compile for quite some time, but suddenly it stopped,
and this is in my log.out: http://pastebin.com/m5cdb08ee

I hope you can help me. I really want to get Python-Ogre working.

[Matej Mo]

> /usr/lib/python2.5/site-packages/pyplusplus/code_creators/calldef_ctypes.py

Well this seems a new bug, because I don't even have the above file.

My compilation was quite messy (I manually installed some libraries,
renamed folders when the script was complaining about versions...
quite a lottery :)) - I actually compiled it 3 times, and had some
libraries installed from previous compilations so I cannot say for
sure what is to be done... Maybe you could try to reinstall py++, or
to try an older version, but I would rather wait for some comments
from the developers or other more knowledgeable people around here.

[Roman Yakovenko]

On Wed, Jan 28, 2009 at 11:01 PM, Olav <olal...@gmail.com> wrote:
>
> Thanks, Matej. I'm one stem closer. I ran
>
> python python-ogre/BuildModule.py -g ogre
>
> And it seemed to compile for quite some time, but suddenly it stopped,
> and this is in my log.out: http://pastebin.com/m5cdb08ee
>
> I hope you can help me. I really want to get Python-Ogre working.

For some reason your pygccxml version is older than needed.

[Olav]

Now, "python python-ogre/BuildModule.py -c ogre" runs for a few hours,
and suddenly fails.

In the log.out, I'm told "/usr/bin/ld: cannot find -lboost_python-
gcc43-mt-1_37".

I think I have tom compile boost (again)? I will try it tomorrow.

On 29 Jan, 06:27, Roman Yakovenko <roman.yakove...@gmail.com> wrote:

[Andy Miller]

This is in the final link stage and it simply means it either can't find the boost library or the name is different (because of 64 bit?)..  Have a look in the ./root/usr/lib directory to see what boost libs are there..

You can override the boost lib name in PythonOgreConfig_posix.py

Andy

2009/1/30 Olav <olal...@gmail.com>

[Olav]

Thank's Andy. I managed to compile ogre, ois and cegui. I've still got
a problem when trying to run the demo files:

"ImportError: libboost_python-gcc43-mt-1_37.so.1.37.0: cannot open
shared object file: No such file or directory"

I should be able to figure it out, but if anyone knows a solution, I
would be happy to know :)

Thanks for some great help.

On 30 Jan, 00:16, Andy Miller <nzmill...@gmail.com> wrote:
> This is in the final link stage and it simply means it either can't find the
> boost library or the name is different (because of 64 bit?)..  Have a look
> in the ./root/usr/lib directory to see what boost libs are there..
> You can override the boost lib name in PythonOgreConfig_posix.py
>
> Andy
>

> 2009/1/30 Olav <olali...@gmail.com>

[Matej Mo]

Did you set the LD_LIBRARY_PATH variable before running the demos?

If yes, then find the file 'libboost_python-gcc43-mt-1_37.so.1.37.0'
with locate and add its path to your LD_LIBRARY_PATH (separate paths
with colon)

[Olav]

Thanks for a fast reply. I fixed it by symlinking /usr/local/lib/ to
the same directory in the source/development folder (root/...)

Now I can run the demos, select openGL, resolution etc. but when I
start them they turn black, and the CPU usage goes like 100%. After
some time, everything on my computer hangs. Any good explanation of
this?

[Matej Mo]

This is the same thing that happens to me. There's actually a huge
memory leak, that eats all the available mem in a few seconds. And
there are no errors in the log.

I can run the native ogre demos and also with java bindings (on Ubuntu
64), so I think that's a python-ogre problem (I sucessfully ran py-
ogre on Linux Mint 32bit)

I hope the devs will look into this, or give a hint what could be
wrong because I'm clueless.

[Olav]

Ok, we should be waiting for Andy, then. I've got 8GB of ram, but it
still hangs. I didn't check the memory usage, but it's probably the
same thing that happens to both of us.

Thanks.

[Andy Miller]

Unfortunately I don't have a 64 bit system to test with :(  Hopefully Tim does and will be able to help ???

Do you know how far the demos get before hanging ??

ie is it in loading a module? Or creating the window etc?

You could testing with demo_spinner as it doesn't use the sample framework although you will have to change the windowhandle creation to something like:

         int64 = False

         for bit in platform.architecture():

             if '64' in bit:

                 int64 = True

         if int64:

             windowHnd = self.renderWindow.getCustomAttributeUnsignedLong("WINDOW")

         else:

             windowHnd = self.renderWindow.getCustomAttributeInt("WINDOW")

Also you could try it without any OIS (input) -- just the Ogre module to see if that fixes things.. (OK so you'll have to kill the window to exit the app :) )..

Andy

2009/1/31 Olav <olal...@gmail.com>

[Matej Mo]

> Do you know how far the demos get before hanging ??

On my machine it hangs alway on the same line in the log: "Parsing

scripts for resource group Autodetect"

Here's the log: http://pastebin.com/m7808657

> You could testing with demo_spinner as it doesn't use the sample framework

I've tried to run it without using SampleFramework (with that window
handle code), but it still hangs

[Matej Mo]

Oh, and I've also tried without OIS, just setting up the basic ogre
objects, and its the same - it always hangs when parsing resource
group Autodetect...

I hope this helps...

[yorick]

I have such problem too on my Debian sid AMD-64. Last message from
script is "Parsing scripts for resource group Autodetect" and python
begin to eat a lot of memory and swap while free space is not over.

[Andy Miller]

Does anyone have a 64 bit system they'd be prepared to offer me ssh access to ??  This way I could at least take an initial look..

Regards

Andy

2009/2/21 yorick <vyo...@gmail.com>

[David Wingate]

Just wanted to add my two cents to both problems on this thread. I'm
also running 64-bit Ubuntu (8.10 intrepid ibix).

1) I had a bunch of boost problems as well. I tracked it down to a
problem
in environment.py; I've attached a patch. This was generated using
the
latest SVN trunk, which I downloaded this morning.

2) I can confirm Matej's problem. Exactly the same thing happens to
me:
I can run the normal OGRE demos without any problems, but the
python-ogre
equivalents always hang when "Parsing scripts for resource group
Autodetect".

I'm not an OGRE expert, so my efforts to debug this quickly got
stonewalled. I
did try ensuring that all of the configuration files were exactly
the same between
the python-ogre demos and the standard OGRE demos, but that
didn't seem
to make a difference.

Andy, I can give you ssh access to my machine. Please email me and we
can
discuss it: wing...@mit.edu.

Thanks,

-- David

Index: environment.py
===================================================================
--- environment.py (revision 904)
+++ environment.py (working copy)
@@ -467,7 +467,7 @@
versionBase = '1_37' ## the version used on the library name

if isLinux():
- bjambase = 'boost-jam-3.1.17-1-linuxx86'
+ bjambase = 'boost-jam-3.1.17'
if is64():
bjambuilddir = 'bin.linuxx86_64'
else:
@@ -475,7 +475,7 @@
bjambuildset = 'gcc'

source = [
- [wget,'http://downloads.sourceforge.net/boost/boost-
jam-3.1.17-1-linuxx86.tgz', downloadPath],
+ [wget,'http://downloads.sourceforge.net/boost/'+bjambase
+'.tgz', downloadPath],
[wget,'http://downloads.sourceforge.net/boost/'+base
+'.tar.gz',downloadPath]
]

On Feb 21, 6:02 am, Andy Miller <nzmill...@gmail.com> wrote:
> Does anyone have a 64 bit system they'd be prepared to offer me ssh access
> to ??  This way I could at least take an initial look..
> Regards
> Andy
>

> 2009/2/21 yorick <vyor...@gmail.com>

[David Wingate]

Incidentally: Matej and Yorick, are you using nvidia cards?

Just wondering, because there's another thread where people
have compiled on 8.10 and it has worked fine. I'm wondering what
the three of us have in common -- it sounds like a 64-bit problem,
but I wonder what else it could be.

-- David

On Feb 25, 9:50 am, David Wingate <winga...@gmail.com> wrote:
> Just wanted to add my two cents to both problems on this thread.  I'm
> also running 64-bit Ubuntu (8.10 intrepid ibix).
>
> 1) I had a bunch of boost problems as well.  I tracked it down to a
> problem
>   in environment.py; I've attached a patch.  This was generated using
> the
>   latest SVN trunk, which I downloaded this morning.
>
> 2) I can confirm Matej's problem.  Exactly the same thing happens to
> me:
>      I can run the normal OGRE demos without any problems, but the
> python-ogre
>      equivalents always hang when "Parsing scripts for resource group
> Autodetect".
>
>      I'm not an OGRE expert, so my efforts to debug this quickly got
> stonewalled.  I
>      did try ensuring that all of the configuration files were exactly
> the same between
>      the python-ogre demos and the standard OGRE demos, but that
> didn't seem
>      to make a difference.
>
> Andy, I can give you ssh access to my machine.  Please email me and we
> can

> discuss it:  winga...@mit.edu.