public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Adam Kropelin <akropel1@rochester.rr.com>
Cc: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] udev-009: Allow build with empty EXTRAS
Date: Wed, 17 Dec 2003 10:34:06 -0800	[thread overview]
Message-ID: <20031217183406.GH6487@kroah.com> (raw)
In-Reply-To: <20031217111114.A3931@mail.kroptech.com>

On Wed, Dec 17, 2003 at 11:11:14AM -0500, Adam Kropelin wrote:
> On Wed, Dec 17, 2003 at 12:31:00AM -0800, Greg KH wrote:
> > On Tue, Dec 16, 2003 at 10:04:06PM -0500, Adam Kropelin wrote:
> > > Need to let the shell expand $EXTRAS so it can properly detect an empty
> > > list. Without this patch, the build fails whenever $EXTRAS is empty.
> > 
> > $ export EXTRAS=
> > $ make
> > $ set | grep EXTRA
> > EXTRAS=
> > $ 
> > 
> > I can't duplicate this problem at all.  Someone else once reported it on
> > the linux-hotplug-devel list, with much the same fix up patch, but later
> > said they couldn't reproduce it either.
> > 
> > What version of make are you using?
> 
> It's actually the version of bash that's important. Prior to 2.05a, bash
> was unable to handle for loops with empty words lists. From the
> bash-2.05a changelog:
> 
> 	p.  `for' loops now allow empty word lists after `in', like the 
> 	    latest POSIX drafts require.
> 
> So bash-2.05 dies on...
> 
> 	for test in ; do echo $test ; done
> 
> ...while bash-2.05a accepts it just fine.
> 
> Both versions can handle this case if the shell itself does the
> expansion that results in the empty list. So that's where my workaround
> came from.

Ah, ok, thanks for the explaination.  I've applied this patch.

greg k-h

      reply	other threads:[~2003-12-17 18:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-17  3:04 [PATCH] udev-009: Allow build with empty EXTRAS Adam Kropelin
2003-12-17  8:31 ` Greg KH
2003-12-17 16:11   ` Adam Kropelin
2003-12-17 18:34     ` Greg KH [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=20031217183406.GH6487@kroah.com \
    --to=greg@kroah.com \
    --cc=akropel1@rochester.rr.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox