"Access denied" error when "./configure"
 

Okay. this is a problem I've had for a while, and I think I'm just getting around to actually asking for help. I cannot install files from source (tar.bz, tar.bz2, tar.gz, etc) my latest attempt began at tuxfiles. following the 'tutorial', if you will, I managed to unpack the files; but when it came to the ./configure step, I got the following error:
Here I figured different distros, slight variances... so instead I tried putting a space in the command (./ configure), and got this error

so finally I tried both ./configure and ./ configure as su and I still got the same errors... this is the same problem that I've always had when installing from source. Can anyone help? I am using Fedora 12. Any help is appreciated.

Is "configure" executable? Try something like "chmod +x ./configure" and then re-run configure.

For future reference, putting "./" before a file or program means that the file exists in the current directory. Your second command "./ configure" therefore is total gibberish to the shell, it thinks you are trying to run the current directory itself, which of course makes no sense.

I guess you are not cd'ing into the directory. Can you see the configure script when you do an ls?

Evo2.

@ MS3FGX
in attempting to chmod, I ran into a new problem: I recieve an error sayingHowever if using chmod -x i get an error saying all in all, I'm very confused here. thank you all for your continued patience.

Hi,

I just downloaded the tarball. As it seems you downloaded the compiled version of it. Just cd into the directory and type
If you want to compile it then download the source from here:
http://www.emutalk.net/showthread.php?t=29643

First, if you are given a command to execute, you should type it exactly as given to you.
Second, seems to me that no configure-script is in your current folder. This can have two reasons:
1. You are not in the correct directory.
2. The program you want to compile simply has no configure-script. In this case it needs not to be configured and you can omit this step.

@crts: Sorry, saw your post too late.

Okay, upon further study, I've found that indeed, @TobiSGD was quite right, and the files had no configure script. It seems unlikely that virtually all the tar.xx files I've ever downloaded, did not have them (I say that because I've Downloaded A LOT of tar.xx files), but indeed, it seems to be the case. I have since installed (successfully) 3 separate tar archives, and indeed those DID have a configure script. Thank you all for your patience with my lack of proper study. But I learned something from it so that kinda makes up for it! :)

I don't know whether or not to mark this as 'solved', seeing as it really shouldn't have been a problem in the first place. but just to be safe, I think I will thanks again for the help