-bash: ./configure: /bin/sh: bad interpreter: Permission denied
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I THINK this happens when the script is formatted in DOS formatting. *nix systems use a differant ASCII code for newlines than DOS and this causes problems if it is formatted in the DOS way. Which ever editor you are using should have an option for the file format to save in.
I'm not sure if you checked this or not, but I remember getting this error when I was building LFS. Turned out my configure script (and a few others) were not exacutable. This wasn't for apache though. Perhaps it might be the same for your situation? You might also want to check any other scripts that is run by configure since I seem to remember this to be a problem under the same program I was trying to compile (sorry I don't remember which one).
regards,
...drkstr
**edit**
Quote:
Plus, it does configure on one machine, but not another...
Hmm, my responce is probably not the answer then. Maybe try 'sh configure --prefix=/usr' just for testing purposes?
That would might do it for you. I've hadd to do an 'upgradepkg --reinstall a/*.tgz' a few times to get me out of a jam. You said it works on the other machine? Just out of curiosity, is their any diffrence in the bash versions? If you're running Slack-10.2, do you have the bash version from the patch directory or the regular a/ directory installed?
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,647
Rep:
Has the partition that stores the files set the exec permission? I had recently the same problem with a Slackbuild script I had started from an vfat partition, and that partition had the noexec attribute set in fstab (or not explicitly set the exec option).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.