Installing on Thecus 5200 NAS

[markbastard]

Hello all.

On my Thecus 5200 NAS I have already installed modules such as SSHD, Python (2.5), etc. I have uploaded sabnzbd to it successfully. Of course when I run it I get an error about the dependencies not being available, e.g. Cheetah template engine.

I can't install Cheetah using the supplied instructions as it's complaining about GCC not being available.

Is there a way around this? Perhaps just uploading a precompiled version of Cheetah? The NAS has a celeron processor so I can possibly build these modules on another machine and up them.

Would really appreciate instructions on how to get these extra dependencies transferred to the NAS in a 'ready to go' state, in the same way that sabnzbd seemed to be 'ready to go' by just transferring it up there.

I'm not that familiar with Python. I'm moderate with linux and fairly advanced with PHP so I should understand concepts etc easy enough, just not the specifics of this app / python.

My goal is to get my NAS to automatically download using RSS feeds in a similar way to using uTorrent on Windows with eztv RSS feeds, ie subscribing to TV shows and have them automatically download. sabnzbd seems like the best candidate for that job (using nzb files of course).

Cheers.

[shypike]

I think most of Cheetah installed anyway, did it not?
The only thing you'll miss is the _namemapper.pyd file, which results only
in a warning at start up and somewhat reduced performance of the web-ui (if you notice it at all).
The PYD file on the Cheetah site is only for Windows! (I assume you do not run Windows on the NAS).

BTW: if you change line 42 of the SetupConfig.py file of the Cheetah distribution, the compilation will be skipped.
So change:

Code: Select all

42:     ext_modules=[Extension("Cheetah._namemapper", [os.path.join("src" ,"_namemapper.c")]

to:

Code: Select all

42:     ext_modules=[]

Good luck.

[markbastard]

Okay, you were correct. I just changed the IF statement above that line from 'posix' to 'posixAAAAAAAAAA' that way it would always go to the else statement and I can just remove the AAAA stuff in future. That got Cheetah installed with no errors.

But of course now I have a new problem!

python setup.py build
running build
running build_py
creating build
creating build/lib.linux-i686-2.5
copying lib/yenc.py -> build/lib.linux-i686-2.5
running build_ext
building '_yenc' extension
creating build/temp.linux-i686-2.5
creating build/temp.linux-i686-2.5/src
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -I/raid/data/module/PYTHON/python/include/python2.5 -c src/_yenc.c -o build/temp.linux-i686-2.5/src/_yenc.o -O2 -g
unable to execute gcc: No such file or directory
error: command 'gcc' failed with exit status 1

Also par2, is that just a standlone exe that needs to exist in the path, is that it?

[shypike]

yEnc isn't needed either, it's there for performance reasons only.

You need par2 and unrar too.
If you find pre-built releases for your system you will have to compile these.

Shouldn't you start looking for the gcc compiler?
Are you running Debian on the box? (http://wpkg.org/Running_Debian_on_Thecus_n5200)
If so, the compiler cannot be a problem.