On Thu, Mar 12, 2009 at 10:31 PM, David O'Brien wrote:
> On Thu, Mar 12, 2009 at 12:48:09PM +0100, Stefan Bethke wrote:
> >> The update still remains broken:
> >> [r...@portjail ~]$ echo $(uname)
> >> -bash: command substitution: line 25: syntax error near unexpected token
> >> `)'
> >> -bash: co
On Thu, Mar 12, 2009 at 12:48:09PM +0100, Stefan Bethke wrote:
>> The update still remains broken:
>> [r...@portjail ~]$ echo $(uname)
>> -bash: command substitution: line 25: syntax error near unexpected token
>> `)'
>> -bash: command substitution: line 25: `uname)'
>
> I also find this rather a
> By any chance, did you commit a Send-PR for this patch? I will
> try the patch later tonight anyway.
> Thanks!
I've submitted a slightly revised patch in a follow-up to an old
PR:
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/101230
It turns out that some of the parser problems with the
> Yes, I can confirm on my system (8-CURRENT i386), switching
> the port from system yacc to bison 2.x solves the
> command substitution problem. Try the attached patch.
I confirm that this patch solves the problem.
Emanuel
pgpQk4iOQmYKE.pgp
Description: PGP signature
On Thu, 12 Mar 2009 14:18:28 -0700 (PDT)
bf wrote:
>--- On Thu, 3/12/09, bf wrote:
>> Hang on guys, we're looking into it. The upstream
>> maintainer
>> confirms that failures in command substitutions are _not_
>> the
>> expected behavior of bash 4.x, that they are not being
>> observed on
>> m
--- On Thu, 3/12/09, bf wrote:
> From: bf
> Subject: Re: shells/bash-4.0 port horribly broken
> To: freebsd-ports@FreeBSD.org
> Cc: obr...@freebsd.org
> Date: Thursday, March 12, 2009, 4:48 PM
> Hang on guys, we're looking into it. The upstream
> maintainer
> conf
On Thu, 12 Mar 2009 13:48:47 -0700 (PDT)
bf wrote:
>Hang on guys, we're looking into it. The upstream maintainer
>confirms that failures in command substitutions are _not_ the
>expected behavior of bash 4.x, that they are not being observed on
>many other systems, and that in the past similar pr
Hang on guys, we're looking into it. The upstream maintainer
confirms that failures in command substitutions are _not_ the
expected behavior of bash 4.x, that they are not being observed on
many other systems, and that in the past similar problems like
this have been connected with problems in bi
Emanuel Haupt wrote:
> The update still remains broken:
>
> [foo...@portjail ~]$ pkg_info
> bash-static-4.0.10_1 The GNU Project's Bourne Again SHell
>
> [r...@portjail ~]$ set -x
> [r...@portjail ~]$ echo $(uname)
> -bash: command substitution: line 25: syntax error near unexpected token `)'
> them work; however, I feel that the easiest thing would be to simply
> revert to Bash-3.
This is exactly what I did.
Emanuel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any ma
On Thu, Mar 12, 2009 at 4:37 PM, Johan van Selst wrote:
> Jerry wrote:
>> Was this some sort of 'improvement' by the Bash developers, or is it
>> an un-squashed bug?
>
> It seems that this might actually be a feature.
> Quoting the COMPAT document of bash4:
>
> 38. Since bash-4.0 now follows Posix
,--- You/Jerry (Thu, 12 Mar 2009 10:30:15 -0400) *
| I am having the exact same problem. Several of my scripts are now
| failing. I have modified a few with the older "`" tic method to make
| them work; however, I feel that the easiest thing would be to simply
| revert to Bash-3.
|
| Was this s
Jerry wrote:
> Was this some sort of 'improvement' by the Bash developers, or is it
> an un-squashed bug?
It seems that this might actually be a feature.
Quoting the COMPAT document of bash4:
38. Since bash-4.0 now follows Posix rules for finding the closing delimiter
of a $() command substit
On Thu, 12 Mar 2009 12:48:09 +0100
Stefan Bethke wrote:
>Am 12.03.2009 um 11:29 schrieb Emanuel Haupt:
>
$ sudo make
===> Vulnerability check disabled, database not found
=> bash-4.tar.gz is not in /usr/ports/shells/bash/distinfo.
=> Either /usr/ports/shells/bash/distinfo is
On Thu, Mar 12, 2009 at 1:48 PM, Stefan Bethke wrote:
> Am 12.03.2009 um 11:29 schrieb Emanuel Haupt:
>
$ sudo make
===> Vulnerability check disabled, database not found
=> bash-4.tar.gz is not in /usr/ports/shells/bash/distinfo.
=> Either /usr/ports/shells/bash/distinfo is ou
Am 12.03.2009 um 11:29 schrieb Emanuel Haupt:
$ sudo make
===> Vulnerability check disabled, database not found
=> bash-4.tar.gz is not in /usr/ports/shells/bash/distinfo.
=> Either /usr/ports/shells/bash/distinfo is out of date, or
=> bash-4.tar.gz is spelled incorrectly.
*** Error code 1
Sto
> > $ sudo make
> > ===> Vulnerability check disabled, database not found
> > => bash-4.tar.gz is not in /usr/ports/shells/bash/distinfo.
> > => Either /usr/ports/shells/bash/distinfo is out of date, or
> > => bash-4.tar.gz is spelled incorrectly.
> > *** Error code 1
> >
> > Stop in /usr/ports/s
On Thu 2009-03-12 08:03:23 UTC+1100, andrew clarke (m...@ozzmosis.com) wrote:
> $ sudo make
> ===> Vulnerability check disabled, database not found
> => bash-4.tar.gz is not in /usr/ports/shells/bash/distinfo.
> => Either /usr/ports/shells/bash/distinfo is out of date, or
> => bash-4.tar.gz is sp
18 matches
Mail list logo
