bash suddenly doesn't like $() syntax

Chuck Robey chuckr at telenix.org
Sat Mar 21 12:01:40 PDT 2009


-----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" <danielby at 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-----


More information about the freebsd-questions mailing list