From: "Mike Jakubik" on
Hello,

It seems that this recent patch introduced a new dependency on bison from
the ports tree. When i performed an portupgrade of 'bash-4.0.33' to
'bash-4.0.33_2' a new dependency for bison appeared. Was this the intended
behavior? I am just curious as it was not needed before.

Thanks.

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Christian Weisgerber on
Mike Jakubik <mikej(a)rogers.com> wrote:

> It seems that this recent patch introduced a new dependency on bison from
> the ports tree. When i performed an portupgrade of 'bash-4.0.33' to
> 'bash-4.0.33_2' a new dependency for bison appeared.

No, the dependency on bison had already been introduced earlier.
(The update to 4.0.33 was in Makefile revision 1.115.)

----
revision 1.111
date: 2009/03/13 15:54:23; author: obrien; state: Exp; lines: +6 -2
Use Bison in the build instead of byacc.
This fixes the issue of '$()' (for ``) not being parsed correctly.

PR: 101230
Submitted by: bf2006a(a)yahoo.com
----

Except that due to the wrong YACC setting the change above didn't
actually do what it was supposed to.

> Was this the intended behavior?

bash 4.0 simply does not build correctly with BSD yacc, it requires
bison. It would be nice if somebody traced this to a bug in yacc
or bash that could be fixed, but so far nobody has done so, and the
GNU people certainly won't bother.

--
Christian "naddy" Weisgerber naddy(a)mips.inka.de

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"