Re: Building with --enable-languages problematic

[Phil Edwards <pedwards at disaster dot jaj dot com>]

On Thu, Oct 11, 2001 at 04:27:20PM +1000, Fergus Henderson wrote:
> On 09-Oct-2001, Phil Edwards <pedwards@disaster.jaj.com> wrote:
> > Something like the completely untested patch, appended?
[...]
> > +		case "${enable_languages}" in
> > +		  # embedded tab -- do not untabify
> > +		  "*[ 	]*") echo configure.in: --enable-languages arguments are not whitespace-separated 1>&2
> > +		             exit 1
> > +			     ;;
> > +		  *)
> > +			     ;;
> > +		esac
> 
> I've been bitten by that one before (using whitespace separators rather
> than comma separators for --enable-languages), so I'm in favour of
> this patch.

Except that it doesn't work, and I don't know why.  Passing something like
--enable-languages="foo bar" always matches the global "*)" case, not the
"* *") case.  (I removed the tab and brackets, and made other silly changes,
all to no avail.)

I thought after almost a decade of coding and syadmining that I knew my
way around Bourne scripting, but now I'm reconsidering.  Any thoughts as
to what I'm missing?

Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams