Bug 1109

Latest stable version is http://imprudence.googlecode.com/files/Imprudence-1.3.1-Linux-x86_64.tar.bz2 for x86_64 & http://imprudence.googlecode.com/files/Imprudence-1.3.1-Linux-x86.tar.bz2 thou the x86-version is deprecated.

Experimental-version for x86 is http://imprudence.googlecode.com/files/Imprudence-1.4.0-Experimental-2011.04.19-Linux-x86.tar.bz2

For x86_64 you have http://imprudence.googlecode.com/files/Imprudence-1.4.0-Experimental-2011.04.19-Linux-x86_64.tar.bz2

Here's the git-hub for the latest source-code:

https://github.com/imprudence/imprudence/network/members

License of Imprudence is GNU GPL v.2

Note that Imprudence are multilicensed.

CC: (none) => odahlum

To get passed the python-celementtree issue you edit fastest_elementtree.py in /linden/indra/lib/python/indra/util/ & uncommenting line 42 to 48.

From row 49 to 59 you delete spaces so it looks like this instead:

try:
        if not use_celementree:
            raise ImportError()
        # Python 2.5 and above.
        from xml.etree.cElementTree import *
        ElementTreeError = SyntaxError
except ImportError:
        # Pure Python code.
        try:
            # Python 2.3 and 2.4.
            from elementtree.ElementTree import *

Now save the changes made & re-run python develop.py & the issue shall disappear. Perhaps a python-error to look at?

I can't get passed my own instructions now that I've tried doing the same thing. I wonder why it worked before.

I even changed the value to False when it comes to using Celementtree & still it doesn't work.

Trying this instruction & seems to compile with make any way:

Do git clone git://github.com/imprudence/imprudence.git in terminal as normal user.

cd to /imprudence/linden/indra & type python develop.py

Let it download & do it's stuff.

You'll get a small error about libGLU.so in the end, but that's no biggie.

Then cd to viewer-linux-<press Tab to get full dir-name>

Now type make

IF I'm not misstaken you'll get to 43% to.

A person from Imprudence-channel in IRC said this about the issue:

"Looks like there's a need to add -lz into the script that links linux-crash-logger or remove viewer-bundled zlib & use system-bundled one."

Theese errors are written here to show you how to solve them in case you run in to them with theese versions as well.

Here are the latest tarballs:

http://code.google.com/p/imprudence/downloads/detail?name=imprudence_1.4.0_beta2_64bit_repacked.tar.gz&can=2&q= for x86_64 & http://code.google.com/p/imprudence/downloads/detail?name=imprudence_1.4.0_beta2_x86.tar.gz&can=2&q= for x86.

Created attachment 1064 [details]
This file contains a text-document with patch-instructions

(In reply to comment #12)
> Created attachment 1064 [details]
> This file contains a text-document with patch-instructions

Thou this doesn't work good enough to fix the compilation.

Redownload the code from the github & replace the current fastest_celementtree.py in /linden/indra/lib/python/indra/util/ with the slightly fixed version of it from above post.

Created attachment 1065 [details]
Here's the replacement file

Now redo the things from comment 8# & in the end of the compilation when you get the liGLU.so-error, depending on your arch go to either /imprudence/linden/libraries/i586-linux/lib_release_client or /imprudence/linden/libraries/x86_64-linux/lib_release_client/ & delete all libGLU and zlib-related so-files & then go to /imprudence/linden/indra/viewer-linux-<press Tab to complete the dir-name> and run make.

If a fix hasn't been added you'll get to 90%.

If you know the fix for this error, please do add instructions on how to solve it.

Thanks.

The last thing to accomplish is that you have to pass -fpermissive to compiler-flags to make warnings non-fatal.

I've successfully compiled a tar.bz2 for Mageia using Mageia 1, but I'm somewhat confused on how to create a good spec-file for it. I downloaded the template spec-file,but I don't know how to form it.

I would be glad if I could get some help.

Assigning this package request to all packagers collectively. On a voluntary basis, one of them might want to integrate it to the distribution and maintain it for bug and security fixes.

 You might also want to join the packager team to maintain this piece of software: see https://wiki.mageia.org/en/Becoming_a_Mageia_Packager

Assignee: bugsquad => pkg-bugs

Since this viewer is no more existing I'll close this as OLD.

Resolution: (none) => OLD
Status: NEW => RESOLVED