Re: #! /bin/sh bash problem
John B. Brown wrote: From: jbb To: bug-bash@gnu.org Subject: gnu software "configure" error Configuration Information [Automatically generated, do not change]: Machine: i586 OS: linux-gnu Compiler: gcc -I/usr/src/packages/BUILD/bash-3.2 -L/usr/src/packages/BUILD/bash-3.2/../readline-5.2 Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i586' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i586-suse-linux-gnu' -DCONF_VENDOR='suse' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib -O2 -march=i586 -mtune=i686 -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -g -D_GNU_SOURCE -DRECYCLES_PIDS -Wall -pipe -g -fPIE -fprofile-use uname output: Linux pinball 2.6.22.17-0.1-default #1 SMP 2008/02/10 20:01:04 UTC i686 i686 i386 GNU/Linux Machine Type: i586-suse-linux-gnu Bash Version: 3.2 Patch Level: 25 Release Status: release Description: Attempting to run 'configure', or any shell script with #! /bin/sh, results in the error message: "bash: ./configure: /usr/bin/bash: bad interpreter: Permission denied" This is generally due to the file permission bits on a program -- in this case /usr/bin/bash -- denying execute access. You might also investigate whether or not /bin/bash is supposed to be symlinked to /usr/bin/bash, which appears to be the case here. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Live Strong. No day but today. Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/
Re: #! /bin/sh bash problem
Dear Bob, Thank you for that reminder of my mortality. Bob Proulx wrote: John B. Brown wrote: Description: Attempting to run 'configure', or any shell script with #! /bin/sh, results in the error message: "bash: ./configure: /usr/bin/bash: bad interpreter: Permission denied" I suspect that the permissions on /usr/bin/bash are preventing you from running it. What does this following say? ls -ld /usr/bin/bash Also, /usr/bin/bash is not a normal location for bash. Normally bash would reside in /bin/bash . Perhaps you also have one there? ls -ld /bin/bash /usr/local/bin/bash Bob [EMAIL PROTECTED]:~ (23):% ls -ld /usr/bin/bash /bin/bash /usr/local/bash /bin/ls: cannot access /usr/local/bash: No such file or directory -rwsrwsr-x 1 root root 604040 2007-09-21 16:16 /bin/bash* -rwxr-xr-x 1 root root 2037410 2008-01-30 05:35 /usr/bin/bash* [EMAIL PROTECTED]:~ (24):% /usr/bin/bash --version GNU bash, version 3.1.0(1)-release (i686-pc-linux-gnu) Copyright (C) 2005 Free Software Foundation, Inc. [EMAIL PROTECTED]:~ (25):% /bin/bash --version GNU bash, version 3.2.25(1)-release (i586-suse-linux-gnu) Copyright (C) 2005 Free Software Foundation, Inc. [EMAIL PROTECTED]:~ Argh! I guess I get to REMOVE the bash I installed in error in that piece of junk location. So much for compiling by myself. I must remember to set the proper --prefix in the configure process; dueling bashes just doesn't make it. Shalom, John B. Brown. [EMAIL PROTECTED] 358 High Street, Buffalo, Wyoming 82834 "Freedom is not worth having if it does not include the freedom to make mistakes" Mahatma Gandhi "It is useless to attempt to reason a man out of what he was never reasoned into." Jonathan Swift "A man who does not know the truth is just an idiot but a man who knows the truth and calls it a lie is a crook." Bertolt Brecht "If any question why we died, tell them, because our fathers lied." Rudyard Kipling
Re: #! /bin/sh bash problem
John B. Brown wrote: -rwsrwsr-x 1 root root 604040 2007-09-21 16:16 /bin/bash* A setuid/setgid root /bin/bash is a really bad idea. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Live Strong. No day but today. Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/
Re: #! /bin/sh bash problem
John B. Brown wrote: > Thank you for that reminder of my mortality. :-) > Bob Proulx wrote: > >Also, /usr/bin/bash is not a normal location for bash. Normally bash > >would reside in /bin/bash . Perhaps you also have one there? > > > > ls -ld /bin/bash /usr/local/bin/bash I suggested looking at /usr/local/bin/bash since that is another typical location. > (23):% ls -ld /usr/bin/bash /bin/bash /usr/local/bash > /bin/ls: cannot access /usr/local/bash: No such file or directory It is probably not an issue here but you looked at /usr/local/bash instead of where I suggested. It didn't exist. I doubt the /usr/local/bin/bash exists either. But I wanted to note that these were different paths. > -rwsrwsr-x 1 root root 604040 2007-09-21 16:16 /bin/bash* How did that happen? Fix that immediately, if not sooner. chmod a=rx,u+w /bin/bash Then also go check other files in your bin directory to make sure you didn't have an errant command set them all. > -rwxr-xr-x 1 root root 2037410 2008-01-30 05:35 /usr/bin/bash* That looks okay. But it doesn't match your previous error message. I assume you were continuing to make changes after your last message because this one shouldn't have given a permission denied one. I expected to see that this wasn't executable at all. > Argh! I guess I get to REMOVE the bash I installed in > error in that piece of junk location. > > So much for compiling by myself. > > I must remember to set the proper --prefix in the configure > process; dueling bashes just doesn't make it. Careful when compiling and upgrading systems in place. A breakage can break your entire system to the point that you might not be able to use it to fix itself. Make sure you have a rescue process available. Bob
Make- 1 error
To: bug-bash@gnu.org Subject: Make- 1 Error (ld) symbol not found Configuration Information [Automatically generated, do not change]: Machine: i386 OS: darwin9.2.2 Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' - DCONF_OSTYPE='dar\ win9.2.2' -DCONF_MACHTYPE='i386-apple-darwin9.2.2' - DCONF_VENDOR='apple' -DLOCA\ LEDIR='/usr/local/share/locale' -DPACKAGE='bash' -DSHELL - DHAVE_CONFIG_H -DMACO\ SX -I. -I. -I./include -I./lib -I./lib/intl -I/Users/bhimmler/ downloads/bash\ -3.2/lib/intl -g -O2 uname output: Darwin william-himmlers-computer.local 9.2.2 Darwin Kernel Versio\ n 9.2.2: Tue Mar 4 21:17:34 PST 2008; root:xnu-1228.4.31~1/ RELEASE_I386 i386 Machine Type: i386-apple-darwin9.2.2 Bash Version: 3.2 Patch Level: 0 Release Status: release Description: -uu-:---F1 bbug1 Top L1 (Fundamental)--- William Himmler [EMAIL PROTECTED]
Re: #! /bin/sh bash problem
Dear Bob, Thank you for your answers. Bob Proulx wrote: John B. Brown wrote: Thank you for that reminder of my mortality. :-) Bob Proulx wrote: Also, /usr/bin/bash is not a normal location for bash. Normally bash would reside in /bin/bash . Perhaps you also have one there? ls -ld /bin/bash /usr/local/bin/bash I suggested looking at /usr/local/bin/bash since that is another typical location. (23):% ls -ld /usr/bin/bash /bin/bash /usr/local/bash /bin/ls: cannot access /usr/local/bash: No such file or directory It is probably not an issue here but you looked at /usr/local/bash instead of where I suggested. It didn't exist. I doubt the /usr/local/bin/bash exists either. But I wanted to note that these were different paths. Actually, nothing exists in /usr/local/bin except space. Personally, the alternative to growing old and senile is not acceptable. -rwsrwsr-x 1 root root 604040 2007-09-21 16:16 /bin/bash* How did that happen? Fix that immediately, if not sooner. chmod a=rx,u+w /bin/bash Then also go check other files in your bin directory to make sure you didn't have an errant command set them all. That setuid/setgid to root was an interim stop-gap prior to asking for help; it is not usual. -rwxr-xr-x 1 root root 2037410 2008-01-30 05:35 /usr/bin/bash* That looks okay. But it doesn't match your previous error message. I assume you were continuing to make changes after your last message because this one shouldn't have given a permission denied one. I expected to see that this wasn't executable at all. Argh! I guess I get to REMOVE the bash I installed in error in that piece of junk location. So much for compiling by myself. I must remember to set the proper --prefix in the configure process; dueling bashes just doesn't make it. Careful when compiling and upgrading systems in place. A breakage can break your entire system to the point that you might not be able to use it to fix itself. Make sure you have a rescue process available. Bob I have rm'd all the symlinks to /bin/bash. I have remade all of them, including a symlink to /usr/bin/bash. If that doesn't finally fix this mess then there is no longer going to be a /usr/bin/bash, binary or link. If this doesn't fill the bill I'll do a find and egrep for 2008 and bash. That will then give me a list of the stuff I need to remove from that tired compile from this past January. Shalom, John B. Brown. [EMAIL PROTECTED] 358 High Street, Buffalo, Wyoming 82834 "Freedom is not worth having if it does not include the freedom to make mistakes" Mahatma Gandhi "It is useless to attempt to reason a man out of what he was never reasoned into." Jonathan Swift "A man who does not know the truth is just an idiot but a man who knows the truth and calls it a lie is a crook." Bertolt Brecht "If any question why we died, tell them, because our fathers lied." Rudyard Kipling
