From: Andreas Schwab <schwab@suse.de>
To: William Stearns <wstearns@pobox.com>
Cc: Giacomo Catenazzi <cate@debian.org>,
ML-linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNONCE] Kernel Autoconfiguration utility v.0.9.1.2
Date: 15 Feb 2001 17:56:39 +0100 [thread overview]
Message-ID: <jeelwzhol4.fsf@hawking.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.30.0102151115170.31520-100000@sparrow.websense.net>
In-Reply-To: <Pine.LNX.4.30.0102151115170.31520-100000@sparrow.websense.net>
William Stearns <wstearns@pobox.com> writes:
|> Good day, Giacomo,
|>
|> On Thu, 15 Feb 2001, Giacomo Catenazzi wrote:
|>
|> > How to use: (now, testing phase)
|> > unpack the files (better: in a new directory)
|> > > bash autoconfigure.sh | less
|> > check the output.
|> > no super user privileges required!
|>
|> Nice work - that's a neat way to do it.
|> One detail; you appear to assume that bash2 is being used. If
|> bash1 is /bin/bash, one gets syntax errors. The following patch allows
|> the script to run under bash1 and bash2, with no noticeable problems.
|>
|> --- autoconfigure.sh-0.9.1.2.orig Wed Feb 14 15:37:30 2001
|> +++ autoconfigure.sh Thu Feb 15 10:59:45 2001
|> @@ -109,7 +109,7 @@
|> }
|> function found () {
|> local conf=CONFIG_$1
|> - if [ "${!conf}" != "y" ]; then
|> + if [ "${conf}" != "y" ]; then
|> define $1 y
|> else
|> debug "$1=y"
This is plain wrong. ${!conf} and ${conf} are completely different
things.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labs completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
prev parent reply other threads:[~2001-02-15 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 10:42 [ANNONCE] Kernel Autoconfiguration utility v.0.9.1.2 Giacomo Catenazzi
2001-02-15 14:34 ` Andrey Panin
2001-02-15 16:20 ` William Stearns
2001-02-15 16:56 ` Andreas Schwab [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jeelwzhol4.fsf@hawking.suse.de \
--to=schwab@suse.de \
--cc=cate@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wstearns@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.