* Nikanth Karthikesan <[EMAIL PROTECTED]> [2008-12-01 12:32:35]:
> On Sunday 30 November 2008 08:38:48 Balbir Singh wrote:
> > * Nikanth Karthikesan <[EMAIL PROTECTED]> [2008-11-29 11:04:10]:
> > > configure script wrongly chooses byacc irrespective of what is available.
> > >
> > > Signed-off-by: Nikanth Karthikesan <[EMAIL PROTECTED]>
> >
> > Thanks for the patch! We have a stronger requirement for byacc, since
> > our library is LGPL and all though bison -y lets to redistribute the
> > generated file under any license we desire from bison version 2.2
> > onwards, provided the derived work itself is not a parser generator.
> >
> > I prefer to use byacc for this work.
>
> I understood this.
>
> I meant to say that it assumes byacc is available even if it is not
> available,
> It was detecting available yacc in a specific order and then just over-rides
> the vaue with byacc.
>
> I had already sent a patch to changes the search order to byacc, bison-y and
> then yacc instead of bison -y, byacc and then yacc.
I see your point, but changing the search order might be bad, but I
guess we do it correctly when packaging using the SPEC file and the
debian package. I'll accept this as a fix for developers who don't
have byacc, but having byacc will continue to remain mandatory for
packaging and distribution.
Anybody feel otherwise? Comments?
--
Balbir
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Libcg-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libcg-devel
