Re: bash suddenly doesn't like $() syntax

2009-03-23 Thread Michael P. Soulier
On Sat, Mar 21, 2009 at 10:20 AM, Lowell Gilbert
freebsd-questions-lo...@be-well.ilk.org wrote:
 Since the update to bash 4.0, the port needs to be built with bison
 instead of the system yacc.  The port has been updated to do this; make
 sure you have version 1.111 of the port's Makefile.

Ok, that's what I have. I'm rebuilding it now.

Mike
-- 
Michael P. Soulier msoul...@digitaltorque.ca
Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction.
--Albert Einstein
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: bash suddenly doesn't like $() syntax

2009-03-23 Thread Michael P. Soulier
On Mon, Mar 23, 2009 at 9:19 AM, Michael P. Soulier
msoul...@digitaltorque.ca wrote:
 Ok, that's what I have. I'm rebuilding it now.

And, confirmed. The rebuilt bash is fine now.

Thanks,
Mike
-- 
Michael P. Soulier msoul...@digitaltorque.ca
Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction.
--Albert Einstein
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: bash suddenly doesn't like $() syntax

2009-03-21 Thread Lowell Gilbert
Michael P. Soulier msoul...@digitaltorque.ca writes:

 I'm running the shells/bash port on 6.3, and I recently ran a portupgrade. All
 of a sudden when I login, my standard .profile and .bashrc are causing a bunch
 of error messages, like so

 -bash: command substitution: line 39: syntax error near unexpected token `)'
 -bash: command substitution: line 39: `})'

 It would see that bash no longer likes the $() command substitution syntax.

 Does that mean that it's defaulting to some sort of posix compatibility mode
 now? 

That syntax *is* in Posix.

Since the update to bash 4.0, the port needs to be built with bison
instead of the system yacc.  The port has been updated to do this; make
sure you have version 1.111 of the port's Makefile.

-- 
Lowell Gilbert, embedded/networking software engineer, Boston area
http://be-well.ilk.org/~lowell/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: bash suddenly doesn't like $() syntax

2009-03-21 Thread Daniel Bye
On Sat, Mar 21, 2009 at 08:49:01AM -0400, Michael P. Soulier wrote:
 Hello,
 
 I'm running the shells/bash port on 6.3, and I recently ran a portupgrade. All
 of a sudden when I login, my standard .profile and .bashrc are causing a bunch
 of error messages, like so
 
 -bash: command substitution: line 39: syntax error near unexpected token `)'
 -bash: command substitution: line 39: `})'
 
 It would see that bash no longer likes the $() command substitution syntax.
 
 Does that mean that it's defaulting to some sort of posix compatibility mode
 now? 

It's a bug in bash 4. It was discussed here a few days ago. I would
deinstall v.4 and install shells/bash3 until the bug's fixed.

Dan

-- 
Daniel Bye
 _
  ASCII ribbon campaign ( )
 - against HTML, vCards and  X
- proprietary attachments in e-mail / \


pgp4WojuUNcqj.pgp
Description: PGP signature


Re: bash suddenly doesn't like $() syntax

2009-03-21 Thread Lowell Gilbert
Daniel Bye danie...@slightlystrange.org writes:

 On Sat, Mar 21, 2009 at 08:49:01AM -0400, Michael P. Soulier wrote:
 Hello,
 
 I'm running the shells/bash port on 6.3, and I recently ran a portupgrade. 
 All
 of a sudden when I login, my standard .profile and .bashrc are causing a 
 bunch
 of error messages, like so
 
 -bash: command substitution: line 39: syntax error near unexpected token `)'
 -bash: command substitution: line 39: `})'
 
 It would see that bash no longer likes the $() command substitution syntax.
 
 Does that mean that it's defaulting to some sort of posix compatibility mode
 now? 

 It's a bug in bash 4. It was discussed here a few days ago. I would
 deinstall v.4 and install shells/bash3 until the bug's fixed.

Which happened a week ago.

-- 
Lowell Gilbert, embedded/networking software engineer, Boston area
http://be-well.ilk.org/~lowell/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: bash suddenly doesn't like $() syntax

2009-03-21 Thread Chuck Robey
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Lowell Gilbert wrote:
 Daniel Bye danie...@slightlystrange.org writes:
 
 On Sat, Mar 21, 2009 at 08:49:01AM -0400, Michael P. Soulier wrote:
 Hello,

 I'm running the shells/bash port on 6.3, and I recently ran a portupgrade. 
 All
 of a sudden when I login, my standard .profile and .bashrc are causing a 
 bunch
 of error messages, like so

 -bash: command substitution: line 39: syntax error near unexpected token `)'
 -bash: command substitution: line 39: `})'

 It would see that bash no longer likes the $() command substitution syntax.

 Does that mean that it's defaulting to some sort of posix compatibility mode
 now? 
 It's a bug in bash 4. It was discussed here a few days ago. I would
 deinstall v.4 and install shells/bash3 until the bug's fixed.
 
 Which happened a week ago.
 

I've had stuff like this happen to me, once in a while.  it's NEVER a fact of
bash really suddenly losing something so major.  What you have to is to look at
previous parts of your code, for things like unclosed parens, unclosed quotes,
things like that.  The errors aren't overly helpful, but if you look at previous
lines, you'll find it there, believe me.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknFMuYACgkQz62J6PPcoOnBjQCeLF31QAwW+hcDfRltl/HBijLz
2DQAnR3riA3EvqU4PDekzdXRQMEfqJH8
=QbQt
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: bash suddenly doesn't like $() syntax

2009-03-21 Thread Chuck Robey
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Lowell Gilbert wrote:

Oh, crap, I flubbed it about the bash error.  It's SO often something claimed by
folks, I knee-jerked that it had to be a previous line in error.  Sorry.
 Daniel Bye danie...@slightlystrange.org writes:
 
 On Sat, Mar 21, 2009 at 08:49:01AM -0400, Michael P. Soulier wrote:
 Hello,

 I'm running the shells/bash port on 6.3, and I recently ran a portupgrade. 
 All
 of a sudden when I login, my standard .profile and .bashrc are causing a 
 bunch
 of error messages, like so

 -bash: command substitution: line 39: syntax error near unexpected token `)'
 -bash: command substitution: line 39: `})'

 It would see that bash no longer likes the $() command substitution syntax.

 Does that mean that it's defaulting to some sort of posix compatibility mode
 now? 
 It's a bug in bash 4. It was discussed here a few days ago. I would
 deinstall v.4 and install shells/bash3 until the bug's fixed.
 
 Which happened a week ago.
 

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknFM1AACgkQz62J6PPcoOm6ZgCdEobknTEk0bl4E5xWGX7uJmBf
zfQAniMO5Isd9x96j/ZCYQdP9fpVtBj1
=hD1K
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: bash suddenly doesn't like $() syntax

2009-03-21 Thread Lowell Gilbert
Chuck Robey chu...@telenix.org writes:

 I've had stuff like this happen to me, once in a while.  it's NEVER a fact of
 bash really suddenly losing something so major.  What you have to is to look 
 at
 previous parts of your code, for things like unclosed parens, unclosed quotes,
 things like that.  The errors aren't overly helpful, but if you look at 
 previous
 lines, you'll find it there, believe me.

That happens, but was not the case in this instance.

A particular syntax really did break in bash if you compiled it with our
system yacc(1).  I don't know whether the problem was in yacc or in the
bash build assuming Gnuisms from bison, but bash really was broken for a
while on $(...) formulations.

-- 
Lowell Gilbert, embedded/networking software engineer, Boston area
http://be-well.ilk.org/~lowell/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org