All of lore.kernel.org
 help / color / mirror / Atom feed
From: miquels@traveler.cistron-office.nl (Miquel van Smoorenburg)
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.19pre3
Date: 22 Dec 2000 17:54:06 GMT	[thread overview]
Message-ID: <9204fu$ghe$3@enterprise.cistron.net> (raw)
In-Reply-To: <20001222173228.A1424@elektroni.ee.tut.fi> <Pine.LNX.3.95.1001222104908.791A-100000@chaos.analogic.com>

In article <Pine.LNX.3.95.1001222104908.791A-100000@chaos.analogic.com>,
Richard B. Johnson <root@chaos.analogic.com> wrote:
>alias kwhich='type -path' in ~./bashrc should fix.

Hmm? Smells like a stupid bug to me. The script is called as:

CCFOUND :=$(shell $(CONFIG_SHELL) scripts/kwhich kgcc gcc272 cc gcc)

So how can bash ever decide to replace scripts/kwhich (OBVIOUSLY
a call to a non-internal command) with an alias or builtin?

Are you sure this is in fact the bug?

Couldn't it be the games with IFS in the scripts/kwhich script?

Try this patch:

--- linux-2.2.19pre3/scripts/kwhich.orig	Tue Dec 19 23:16:52 2000
+++ linux-2.2.19pre3/scripts/kwhich	Fri Dec 22 19:02:47 2000
@@ -7,7 +7,7 @@
         exit 1
 fi
 
-IFS=:
+IFS=":$IFS"
 for cmd in $*
 do
         for path in $PATH


Mike.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-12-22 18:24 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-22  0:52 Linux 2.2.19pre3 Alan Cox
2000-12-22  3:40 ` Mitch Adair
2000-12-22 15:32 ` Petri Kaukasoina
2000-12-22 15:53   ` Richard B. Johnson
2000-12-22 16:02     ` Chad Schwartz
2000-12-22 16:23       ` Alan Cox
2000-12-22 16:25         ` Chad Schwartz
2000-12-22 16:43         ` Richard B. Johnson
2000-12-22 17:54     ` Miquel van Smoorenburg [this message]
2000-12-22 18:13       ` Richard B. Johnson
2000-12-22 16:21   ` Alan Cox
2000-12-22 19:33 ` Petri Kaukasoina
2000-12-22 19:56   ` Andrea Arcangeli
2000-12-23 12:05 ` Willy Tarreau
2000-12-28  1:18 ` Matthias Andree
2000-12-28  2:37   ` Alan Cox
2000-12-28 10:23     ` Matthias Andree
2000-12-28 12:20       ` Alan Cox
2000-12-28 13:53         ` Linux 2.2.18: /proc/apm slows system time (was: Linux 2.2.19pre3) Matthias Andree
2000-12-28 14:14           ` Matthias Andree
2000-12-29 12:42           ` Erik Mouw
2000-12-30 12:39             ` Matthias Andree
2000-12-30 17:01               ` Alan Cox
2000-12-30 17:38                 ` Erik Mouw
2000-12-30 17:50                   ` Alan Cox
2000-12-30 17:39                 ` Matthias Andree
2000-12-31 10:34                 ` Matthias Andree
2000-12-31 11:28                   ` Chris Wedgwood
2000-12-31 13:32                     ` Alan Cox
2001-01-02 13:52                       ` [PATCH] CMOS locking for 2.4 (was: /proc/apm slows system time) Paul Gortmaker
2000-12-31 13:37                   ` Linux 2.2.18: /proc/apm slows system time (was: Linux 2.2.19pre3) Alan Cox
2000-12-31 15:50                     ` Erik Mouw
2000-12-31 16:13                       ` Alan Cox
2001-01-02 16:32                     ` Matthias Andree
2001-01-02 17:31                       ` Alan Cox
2001-01-03 22:02                         ` Matthias Andree
2000-12-28 11:14     ` Linux 2.2.19pre3 Guest section DW

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='9204fu$ghe$3@enterprise.cistron.net' \
    --to=miquels@traveler.cistron-office.nl \
    --cc=linux-kernel@vger.kernel.org \
    /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.