On 03/05/06 04:12, Rainer Alves wrote:
> Kris Kennaway wrote:
>> On Sun, Mar 05, 2006 at 09:57:54AM +0100, Nicolas Rachinsky wrote:
>>> * Kris Kennaway <[EMAIL PROTECTED]> [2006-03-05 03:41 -0500]:
>>> > On Sun, Mar 05, 2006 at 09:36:25AM +0100, Nicolas Rachinsky wrote:
>>> > > The problem seems to depend on the installed bison version. With no
>>> > > bison or bison-2.1_1 installed it works fine, with bison-1.75_2,1 it
>>> > > doesn't.
>>> > > Installed at what point: the build time of the bash port, or runtime
>>> > (which would be very odd)?
>>>
>>> The build time. I submitted ports/94086, which contains a
>>> fix/workaround.
>>
>> Great, thanks for tracking this down!  Can others confirm this
>> solution?
> 
> Yes, this fixes the problem. Using devel/bison2 instead of 1.75 also
> works, but switching to the builtin YACC is indeed a better solution.

I had yacc/bison problems when attempting to build the csup port.  I've
previously had issues with install-info/texinfo:
http://lists.freebsd.org/pipermail/freebsd-questions/2006-February/114123.html

The real issue was that I had changed my path to put /usr/local/(s)bin
before /usr/(s)bin.  I've since changed my path back and everything
works as expected.  I don't even recall why I changed it in the first
place, but it caused some interesting problems...

-Jonathan

-- 
Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to