Re: bash 4.2 patchlevel 28

2012-05-31 Thread Sean Bruno 
On Wed, 2012-05-30 at 20:19 -0700, David O'Brien wrote:
> On Thu, May 24, 2012 at 01:07:55PM -0700, Sean Bruno wrote:
> > Noted that the following syntax is broken somewhere between 4.2
> > patchlevel 10 and 28.  I'm sure its because we shouldn't be doing that
> > over here at big purple, but we do ... and its a PITA.  I'm bisecting to
> > find out what is going on.
> 
> Hi Sean,
> Were you able to track down which patch 10-28 broke this for you?
> 
> thanks,

After reverting back to patchlevel 10, I applied patches sequentially.
something about patchlevel 12 caused issues for our homebrew builds via
m4/bison that I haven't investigated.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: bash 4.2 patchlevel 28

2012-05-30 Thread David O'Brien 
On Thu, May 24, 2012 at 01:07:55PM -0700, Sean Bruno wrote:
> Noted that the following syntax is broken somewhere between 4.2
> patchlevel 10 and 28.  I'm sure its because we shouldn't be doing that
> over here at big purple, but we do ... and its a PITA.  I'm bisecting to
> find out what is going on.

Hi Sean,
Were you able to track down which patch 10-28 broke this for you?

thanks,
-- 
-- David  (obr...@freebsd.org)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: bash 4.2 patchlevel 28

2012-05-28 Thread Christian Weisgerber 
Sean Bruno  wrote:

> > > VARIABLE="$(uname)"
> > > bash: command substitution: line 3: syntax error near unexpected token
> > > `)'
> > > bash: command substitution: line 3: `uname)"'
> > > 
> > At least that was easy.  It's patch level 12.

That's just the first patch that happens to touch parse.y.

> Hrm ... and it also appears that if I use bison + m4 I don't have this
> issue, but if I let the configure scripts use /usr/bin/yacc alone this
> problem manifests itself.  odd.

The port specifically uses bison, so I don't know why you would
force the use of yacc.  And it's a well-known issue.  If you run
parse.y through yacc, it breaks.  You must use bison.

Upstream thinks it's a bug in yacc unless proven otherwise and so
far nobody has figured out the details.

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: bash 4.2 patchlevel 28

2012-05-25 Thread Jason Hellenthal 


On Fri, May 25, 2012 at 07:44:39AM +0200, Trond Endrest?l wrote:
> On Thu, 24 May 2012 13:07-0700, Sean Bruno wrote:
> 
> > Noted that the following syntax is broken somewhere between 4.2
> > patchlevel 10 and 28.  I'm sure its because we shouldn't be doing that
> > over here at big purple, but we do ... and its a PITA.  I'm bisecting to
> > find out what is going on.
> > 
> > test:
> > VARIABLE="$(uname)"
> > bash: command substitution: line 3: syntax error near unexpected token
> > `)'
> > bash: command substitution: line 3: `uname)"'
> > 
> > Odd, but his works at patchlevel 10
> 
> I'm unable to reproduce this behaviour on one of my systems:
> 
> trond@enterprise:~>bash --version
> GNU bash, version 4.2.28(0)-release (amd64-portbld-freebsd9.0)
> Copyright (C) 2011 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later 
> 
> 
> This is free software; you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> trond@enterprise:~>my_var="$(uname)"
> trond@enterprise:~>echo $my_var
> FreeBSD
> trond@enterprise:~>
> 
> I'm not sure what's going on in your case.
> 

Same here but on 8.3-STABLE i386 no errors found throughout any of the
tests.


-- 

 - (2^(N-1))
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: bash 4.2 patchlevel 28

2012-05-24 Thread Trond Endrestøl 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, 24 May 2012 13:07-0700, Sean Bruno wrote:

> Noted that the following syntax is broken somewhere between 4.2
> patchlevel 10 and 28.  I'm sure its because we shouldn't be doing that
> over here at big purple, but we do ... and its a PITA.  I'm bisecting to
> find out what is going on.
> 
> test:
> VARIABLE="$(uname)"
> bash: command substitution: line 3: syntax error near unexpected token
> `)'
> bash: command substitution: line 3: `uname)"'
> 
> Odd, but his works at patchlevel 10

I'm unable to reproduce this behaviour on one of my systems:

trond@enterprise:~>bash --version
GNU bash, version 4.2.28(0)-release (amd64-portbld-freebsd9.0)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
trond@enterprise:~>my_var="$(uname)"
trond@enterprise:~>echo $my_var
FreeBSD
trond@enterprise:~>

I'm not sure what's going on in your case.

- -- 
+---++
| Vennlig hilsen,   | Best regards,  |
| Trond Endrestøl,  | Trond Endrestøl,   |
| IT-ansvarlig, | System administrator,  |
| Fagskolen Innlandet,  | Gjøvik Technical College, Norway,  |
| tlf. dir.   61 14 54 39,  | Office.: +47 61 14 54 39,  |
| tlf. mob.   952 62 567,   | Cellular...: +47 952 62 567,   |
| sentralbord 61 14 54 00.  | Switchboard: +47 61 14 54 00.  |
+---++

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.18 (FreeBSD)

iEYEARECAAYFAk+/HEwACgkQbYWZalUoElvZYwCeLq5IHGp2dLyf+pcbzC1jk3RK
us4An1AX5SelbwMEEVmooiopPmF9SAlI
=9bTW
-END PGP SIGNATURE-___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: bash 4.2 patchlevel 28

2012-05-24 Thread Sean Bruno 
On Thu, 2012-05-24 at 13:14 -0700, Sean Bruno wrote:
> 
> On Thu, 2012-05-24 at 13:07 -0700, Sean Bruno wrote:
> > Noted that the following syntax is broken somewhere between 4.2
> > patchlevel 10 and 28.  I'm sure its because we shouldn't be doing that
> > over here at big purple, but we do ... and its a PITA.  I'm bisecting to
> > find out what is going on.
> > 
> > test:
> > VARIABLE="$(uname)"
> > bash: command substitution: line 3: syntax error near unexpected token
> > `)'
> > bash: command substitution: line 3: `uname)"'
> > 
> > Odd, but his works at patchlevel 10
> > 
> > sean
> 
> At least that was easy.  It's patch level 12.  Sequential sort pays
> dividends today.
> 
> Sean
> 


Hrm ... and it also appears that if I use bison + m4 I don't have this
issue, but if I let the configure scripts use /usr/bin/yacc alone this
problem manifests itself.  odd.

sean

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: bash 4.2 patchlevel 28

2012-05-24 Thread Sean Bruno 


On Thu, 2012-05-24 at 13:07 -0700, Sean Bruno wrote:
> Noted that the following syntax is broken somewhere between 4.2
> patchlevel 10 and 28.  I'm sure its because we shouldn't be doing that
> over here at big purple, but we do ... and its a PITA.  I'm bisecting to
> find out what is going on.
> 
> test:
> VARIABLE="$(uname)"
> bash: command substitution: line 3: syntax error near unexpected token
> `)'
> bash: command substitution: line 3: `uname)"'
> 
> Odd, but his works at patchlevel 10
> 
> sean

At least that was easy.  It's patch level 12.  Sequential sort pays
dividends today.

Sean

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"