Hi,
on suse I could type ./setup.sh in the KDE terminal, but now in Gentoo this does not work, I have to type sh setup.sh
Also in Suse I could click on a setup.sh on a CDROM and it would execute now I can't.

I am sure it's something I can set to get the same functionality in Gentoo.

Do you have execute permissions on the file? ls -l file.sh will show something like this :
-rw-r--r-- 1 recluse users 5008 May 14 19:12 foo.txt
Notice the lack of x's in where every 3rd - is? That means that I can't execute the file.
Do 'chmod u+x file.sh' to add execute permissions.

Do you have execute permissions on the file? ls -l file.sh will show something like this :
-rw-r--r-- 1 recluse users 5008 May 14 19:12 foo.txt
Notice the lack of x's in where every 3rd - is? That means that I can't execute the file.
Do 'chmod u+x file.sh' to add execute permissions.

I have a CD with a setup.sh, and on suse 8.0 I can just click on it in the KDE file manager and it launches the setup program.
On Gentoo it KDE just reports that setup.sh cannot be found and craps out.
My cdrom has exec in the fstab, I even copied all the files to my home dir and it still won't work.
All the permission are correct.
if I open a terminal and type ./setup.sh it starts to run but then dies becasue it can't find a .so that is in the same directory.

Why is it that it runs in Suse and Redhat , but not Gentoo. I am sure I have something configured wrong or not at all, but I don't know what.
This is a commercial CD that works on every other modern distribution.

Hmm.. well, it fails from the commandline, so thats probably why KDE is having issues with it through run.

As for why it is failing on the commandline, we need to use deduction. What application is it? Check out the setup.sh, what is it doing? usually it's something simple like a binary it's calling that is having the issue. If it is, you can run "ldd <binary name>" and it should tell you what libraries it's going to use. If any are missing, or something it'll tell you kinda rudely.

place a symlink of the .so file into your /usr/bin directory. This will tell you if it's a path issue or some other issue. (or, just cp the .so file to /usr/bin.)

if that doesn't work, check your permissions again. I know you said you set them all correctly, but give it another shot. Just for giggles, set that entire folder to 777 if you can (use the -R flag) Again, that will tell you if its a permissions issue or not.

This may not completely solve the issue, but it should at least allow you to narrow down the cause of the problem.

--kurt_________________The problem with political jokes is that they get elected

I think I may have found the problem:
Kylix basically needs to have a file in /usr/lib or /lib named
libstdc++-libc6.1-1.so.2. This file should be a symbolic link
to the C++ library, which will also be in /usr/lib or /lib and
have a name that fits the pattern libstdc++*.so. So, for
example, if you look in /usr/lib and find a file called
libstdc++-3-libc6.1-2-2.10.so, you would enter the following
shell commands to create the symbolic link: