On Sat, 28 Feb 2004, Julio M. Merino Vidal wrote:

> If I do that, tools.mk only tries to provide a yacc utility that is good
> enough to work for most programs.  But I want the GNU flavour of it, not one
> that may work.  So I find this confusing...

Yes, this has been mentioned before, so would be good to fix.

> What about changing tools.mk so that USE_GNU_TOOLS _always_ picks up a GNU
> variant (it could check if the base system provides it to avoid
> reinstallation), and add a USE_TOOLS that can be used to mark a package as
> needing some special tools?
>
> I.e., you do:
>
> USE_TOOLS+= yacc lex
>
> then, tools.mk will try to provide a yacc and a lex that work, as it actually
> does.
>
> But if you do:
>
> USE_GNU_TOOLS+= yacc lex
>
> then you always get the GNU versions.

That all sounds good.

> Or maybe make USE_GNU_TOOLS recognize 'bison' as another "different" utility
> that explicitly pulls bison in?

That should be fine too, but I'd prefer your previous suggestion.

Also, before when I had problems with bison, I packaged up a BSD yacc for
Linux.  (byacc in pkgsrc-wip.)

   Jeremy C. Reed
   http://www.reedmedia.net/