I am new to Linux, I have Suse 8.2, running KDE 3.2.

I want 'karamba', so I downloaded the karamba-0.17.tar.gz file.

How in the world do I get the program to run. Installing an application is so incredibly frustrating. There are no .exe files in Linux! No "Setup" files! Can somebody please hlep me install this application so that I can use it? Thanks for your time and consideration.

cd to the directory where the file is

tar xvzf karamba-0.17.tar.gz

it'll extract the files into karamba-0.17 directory
cd in there, then read the readme (could be in docs\)
but as a general guide, for installing binaries they will usually include an installation script, which they'll tell you in the readme file. For installing from sources (you'll see a Makefile in the directory) generally you do
./configure
make
make install
but depending on the application it might have extra procedures, read the documentations.
for .tar.bz2 files you use "tar xvjf" instead

Thank you for taking the time to respond, Demonbane. When implementing your suggestion, (of which I alredy had), I get the following error:

configure: error: no acceptable C compiler found in $PATH

So, here's my question. Where do I get this "compiler"? I'm running SuSE 8.2

Here are the "Basic" (yeah, right!) Installation Instructions for the karamba-0.17 file.


Basic Installation
==================

These are generic installation instructions.

The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').

If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.

The file `configure.in' is used to create `configure' by a program
called `autoconf'. You only need `configure.in' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.

The simplest way to compile this package is:

1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.

Running `configure' takes a while. While running, it prints some
messages telling which features it is checking for.

2. Type `make' to compile the package.

3. Type `make install' to install the programs and any data files and
documentation.

4. You can remove the program binaries and object files from the
source code directory by typing `make clean'.

Compilers and Options
=====================

Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
this:
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure

Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure

Compiling For Multiple Architectures
====================================

You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.

If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.

Installation Names
==================

By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.

You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.

If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Optional Features
=================

Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.

For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.

Specifying the System Type
==========================

There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on. Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
CPU-COMPANY-SYSTEM

See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.

If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.

Sharing Defaults
================

If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.

Operation Controls
==================

`configure' recognizes the following options to control how it
operates.

`--cache-file=FILE'
Use and save the results of the tests in FILE instead of
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
debugging `configure'.

`--help'
Print a summary of the options to `configure', and exit.

`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made.

`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.

`--version'
Print the version of Autoconf used to generate the `configure'
script, and exit.

`configure' also accepts some other, not widely useful, options.

Ok trying installing every RPM that starts with the word "gcc" from your suse8.2 cdrom

update: yeah try Megamieuwsel's suggestion, I don't use Suse so I'm not exactly sure how does it manage it's packages.

Looks like you haven't installed it with your system.
Running SuSE8.2 myself.
What were the install-choices you made?
Better do a "update with patch-cd" in the Yast2-menu , using your original diskset and install the devlopment toolsets.

And you might want to look for a little more libraries there as well ; there's an option , somewhere in there , I only stumbled across by incident : You can install a couple of libs for compatabillity with older SuSE versions.
Look for that as well ; You'll be a happier human with those installed.

I did that, I installed every kind of C compiler I could find via YaST2. Now, I get an error when typeing "make".

what's the error message?

Here's the error message at the end of the script that it has run.

==============
checking for Qt... configure: error: Qt (>= Qt 3.0) (headers and libraries) not found. Please check your installation!
For more details about this problem, look at the end of config.log.
==============

Where do I go from here?

I got the following information from the author's site:

=================
The usual installation steps:

Untar the source package
cd to the new directory and then type:


# ./configure && make
# su -c "make install"

A compile problems with Red Hat 8 has been reported.
The problem was in this case solved by adding typing:


# make -f Makefile.cvs && ./configure && make
============


Now, I've tried the first set of command lines but I get the following error:

======
checking for Qt... configure: error: Qt (>= Qt 3.0) (headers and libraries) not found. Please check your installation!
For more details about this problem, look at the end of config.log.
======

So when I run the second set of commands, I get the following errror:

==========
su: user install does not exist
==========

Now, when I type the line,

=======
make -f Makefile.cvs && ./configure && make
=======

It runs a script, and then I get the following error:

========
checking for Qt... configure: error: Qt (>= Qt 3.0) (headers and libraries) not found. Please check your installation!
For more details about this problem, look at the end of config.log.
========

Can you help?

I may have found the solution. I found a "HowTo" for karamba. Let me know if anyone has implmented this and got it working using THIS "How To".

==========
Karamba Mini-How-To for RH8
Last Revised 04-08-03
email: rootnuke@yahoo.com


Some might find these instructions painfully detailed others may find them
helpful. Everything to follow is a culmination of everything I found on the
posts which allowed me to successfully install Karamba on several RedHat v8.0
stations. I hope this helps.

{} = contain variable items which are unique to your system such as username
and password as in {secret}

"" = exact input like "bob"

[] = keys to punch like [ctrl]+[alt]+[backspace]

Comments and suggestions are welcome! Send to rootnuke@yahoo.com

DOWNLOADING KARAMBA, SCRIPTS AND THEMES
Download latest version of Karamba and Scripts from
http://www.efd.lth.se/~d98hk/karamba/
into your home directory.

Using Konquerer or some other GUI file manager create a directory in your home
directory called karamba. Create a folder called scripts and themes within the
Karamba folder.

Double click on each downloaded karamba, script and theme tar file revealing
the compressed folder within. Right click and copy the folder within and paste
them into scripts folder or themes folder in the karamba directory. Do the
same for the Karamba tar and paste it into your /home directory NOT in the
karamba directory you created. The karamba tar will have its own name, see
below.

The end result will be;

/home/karamba-X.XX/source files
/home/karamba/script
/home/karamba/themes

Note: You can have your script and theme files anywhere you want. I like the
home directory because it's easier for me. In addition when it comes time to
move or upgrade all my karamba and other stuff it is in one spot and easy to
transfer to transfer another box.

MAKE SURE YOU HAVE NEEDED PACKAGES
Open a Konsole session and make sure you have the following packages
installed on your system;

kdelibs-devel
qt-devel
libart_lgpl-devel
libart_lgpl

Do this by typing rpm -q packagename.
For example: rpm -q qt-devel


KARAMBA INSTALLATION
Open a Konsole terminal session which should default to your home
directory and change into the karamba-X.XX directory by typing;

cd karamba-0.15

Depending on your version of Karamba your directory name will vary.

Now it's time to compile and install Karamba. Inside the Karamba-X.XX
directory type the following.

Note: Karamba's site specifies the command for ./configure as
./configure --prefix=/usr && make
...this failed on my installation.)

What worked for me was the following;

make -f Makefile.cvs && ./configure && make
su
{yourpassword}
make install

MAKE YOUR SCRIPTS EXECUTABLE
If you will have your scripts and themes in a place other than your home
directory you will use the File Manager - Super User file manger GUI to change
the scripts to executable. File Manager - Super User is located in Extras -
System Tools - File Manager Super User Mode. Otherwise just use your regular
GUI file manager to change the files. To change the files to executable right
click on each file and select Properties, Permissions and check Exec. Perform
this change on each of your scripts located in /home/karamba/scripts.

SETTING YOUR PATHING TO SCRIPTS DIRECTORY
In order for you to run the script it must be in the search path of your
system. Run your file browser select View and select Show Hidden Files. Right
click on the file .bash_profile. Right click the file and select Open with....
Text Editor. Place a # sign to remark out the current PATH command and place
the following path command below;

PATH=$PATH:/home/{yourname}/karamba/scripts:$HOME/bin

Note: {yourname} is the directory name in the system home directory
Example: If your home directory name is bob then your path would be;
PATH=$PATH:/home/bob/karamba/scripts:$HOME/bin

Note: Review your changes carefully. If you mis-type your x server will not
restart because the pathing is screwed up. I speak from experience.
Thats why you put the # to remark the original line out for your path.
Remember, never burn your bridges, you may have to retreat!

I personally like the Konsole method so for the text non-GUI oriented, open a
Konsole terminal session edit the .bash_profile file which is a hidden file in
your home directory. Your command to open and edit the file as above would be;

pico .bash_profile

To run the .bash file to make your changes take effect type;
source .bash_profile

To determine if the changes did take effect you can run;
echo $PATH

You should see your new path in the listing along with any other paths that
were in your path string.

More information regarding path instructions can be found at RedHat
http://www.redhat.com/docs/manuals/l...-starting.html

Close all your programs and restart your X server with [ctrl]+[alt]+[backspace]

TRY IT OUT
Open your Konsole and type karamba. Select your theme in
/home/{yourname}/karamba/themes/whatever.theme

Right click on the theme window and adjust as desired. If the theme is empty
then you need to check either your pathing or script executable steps above.

MAKING IT PRETTY
Now that Karamba works manually the next step is to have it auto start on boot
and place your themes in the exact coordinates that best fits your wallpaper,
icons etc.

First of all it is presumed that you are keeping themes in
/home/{yourname}/karamba/themes and scripts in
/home/{yourname}/karamba/scripts.

Run your File Manager - Super User gui file manager and change into your home
directory and change your View to Show Hidden Files with View, Show Hidden
Files. Look for .kde directory and change into it. Right click in the empty
area and select Create New, Link to Application.

The properties dialog box will appear which has 4 tabs entitled, General,
Permissions, Execute and Application. Type in the empty field in the General
tab "karamba_linuxtoday.desktop" without the "". It should be noted that this
file could be named anything as long as it is within the file name contraints
of Linux. Its named karamba because that is the application we will run and
the balance is the theme description which will be LinuxToday a news feed.
"desktop" is again descriptive for its purpose.

Next select the Permissions. My permissions have "root" in the user and group
name with User RW, Group R and Others R for Access Permissions. Just leave it
the way it is.

Select the execute tab and type in the empty Command filed your command line to
run. In this example we will be setting a newsfeed from LinuxToday which is
available at http://www.kde-look.org. To run, the command will read;
'/usr/bin/karamba' /home/{yourname}/karamba/themes/websites/linux_today.theme

Note: Yes you need the '' on each side of /usr/bin/karamba. Also the directory
name "websites" was a part of the theme package directory structure so that is
why it is in the command structure.

Leave the Application tab at default. Press OK. If you have done everything
right you should be able to relog and have your new theme autostart.

Ok, you've rebooted or relogged and wow there it is. But it's not quite in the
right place, hmmm. If you do not want to have to adjust and align every time
you boot especially if you have 4 or 5 themes then you will need to edit the
coordinates in the theme file.

Open your Konsole terminal and type karamba then choose your theme. Once your
theme runs the right click on it select Toggle Locked Position. now move the
theme to where you want it. As you move the theme let go and your "Window"
coordinates will appear in the Konsole session. Note the line that is last.
Mine says Window X=250 Y=40, write it down. Close the Konsole session.

Open your Konsole terminal (not the gui file manager) and type
pico linux_today.theme which will open the theme file for editing. Looking at
the very top line which begins Karamba change the X= and Y= to your
coordinates as noted. To exit type [ctrl]+[x], [Y], [Enter] to exit.

Note: Use pico or vi as an editor. Other editors may leave hidden characters
which cause the theme to fail.

OK, relog and view your Karamba autostart in just the right location on your
desktop. :0 UUUUU Impress your friends and neighbors as they view your desktop
in wonderment. :-)

=============

Well looks like you need

kdelibs-devel
qt-devel
libart_lgpl-devel
libart_lgpl

installed first in order to be able to use it
you should be able to find them on your suse8.2 CD

Demonbane, thank you. I'll be sure to install those apps first. When I have time later tonight, I'll give a crack at it. Thanks!