.: Enviroment Checker :.

fergy

Member ++
Joined
Jan 11, 2007
Messages
170
Reaction score
3
Location
croatia
Here is simple script who will check necessary tools what is needed for compiling Dreambox/Dbox/TD image under Linux enviroment.

#1 Unzip it and put into Your tuxbox-cvs/cdk directory
#2 execute it by typing in terminal: ./checker.sh

NOTE: You MUST BE LOGIN AS ROOT.

How to do that?

#1 Open terminal and execute comand
Code:
You don't have permission to view the code content. Log in or register now.
( hit Enter )

( su command mean: super user - root )

#2 Enter Your root password ( hit Enter )
#3 cd into tuxbox-cvs/cdk by executing command:
Code:
You don't have permission to view the code content. Log in or register now.

( hit Enter )

#4 execute command:
Code:
You don't have permission to view the code content. Log in or register now.

( hit Enter )

NOTE: This will take a while so be patient.

Here is sample how it look:

Code:
You don't have permission to view the code content. Log in or register now.

So, as You see, Yellow marked is what is needed and Green marked is what I have ( version must be similar or bigger )
PS This script will NOT mark You anything with colors. : colors1
 
Last edited:
Fergy,

I think you forgot to attach the script :(

Wiggy
 
it should say
root@tonymills-desktop:~/tuxbox-cvs/cdk$
Code:
You don't have permission to view the code content. Log in or register now.
if your not in as root then Permission denied is what you will get.

mksquashfs is in the cvs or will be after compiling.
monotone isn't needed for dm500 (thought it was only enigma 2 compiles ?)
svn (subversion) (is not needed).
 
Code:
You don't have permission to view the code content. Log in or register now.

This:

Code:
You don't have permission to view the code content. Log in or register now.

is because You was not execute command as root.

And this:

Code:
You don't have permission to view the code content. Log in or register now.

is for openembedded-bitbake systems-You will not needed for CVS ( Enigma1 )

So, please login as root ( Ubuntu users use command sudo ) and execute it again.
Cheers
 
Back
Top