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,
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
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
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:
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
-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
-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
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
