1832459 Members
3095 Online
110043 Solutions
New Discussion

./configure

 
SOLVED
Go to solution
Ceaser123
Occasional Advisor

./configure

Why do I have to do a chmod on ./configure when it is obvious that I need to run it. Didn't the author know this or am I missing something?
2 REPLIES 2
Jeff Schussele
Honored Contributor
Solution

Re: ./configure

Hi,

It depends on how the file arrives.
If it's created on the system, then there's no way to give it executable perms at creation - you have to do that manually or via a script command. It's a UNIX rule.
If it's packaged then I'd agree that it was an oversight.

Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
A. Clay Stephenson
Acclaimed Contributor

Re: ./configure

Probably because when you untar'ed, uncpio'ed, ... the package you were under a very restrictive umask. If you don't know what that means then you are missing something.
If it ain't broke, I can fix that.