Re: bash problem

[waibel <waibel1@gmx.de>]

Es ist eine Standard Sckript.
Der Anfang des Skriptes ist:
#!/bin/sh

### WARNING: this file contains embedded tabs.  Do not run untabify on this 
file.

# Configuration script
# Copyright (C) 1988, 90, 91, 92, 93, 94, 95, 96, 97, 98, 1999
# Free Software Foundation, Inc.

# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.

# This file was originally written by K. Richard Pixley.

#
# Shell script to create proper links to machine-dependent files in
# preparation for compilation.
#
# If configure succeeds, it leaves its status in config.status.
# If configure fails after disturbing the status quo,
#       config.status is removed.
#

echo starting configure

export PATH || (echo "OOPS, this isn't sh.  Desperation time.  I will feed 
myself to sh."; sh $0 $argv; kill $$)

remove=rm
hard_link=ln
symbolic_link='ln -s'

#for Test
#remove="echo rm"
#hard_link="echo ln"
#symbolic_link="echo ln -s"







Am Freitag, 8. Februar 2002 13:13 schrieb Johannes Franken:
> X-Loo
> p: debian-user-german@lists.debian.org
> Precedence: list
> Resent-Sender: debian-user-german-request@lists.debian.org
>
> On Fri, Feb 08, 2002 at 12:12:26PM +0100, franz wrote:
> > Wenn ich bestimmte Skripts (./configure) laufen lassen will, bekomme ich
> > eine Fehlermeldung von der Shell "bash: ./configure: /bin/sh: bad
> > interpreter:
>
> Wie lautet die erste Zeile des betroffenen Scripts,
> und was passiert, wenn Du den Text hinter #! in der Shell eingibst?