Menu
▾
▴
[Sblim-issues] [ sblim-Bugs-1203835 ] make fails on yacc command
|
From: SourceForge.net <no...@so...> - 2005-08-29 23:45:16
|
Bugs item #1203835, was opened at 2005-05-17 12:43 Message generated for change (Comment added) made by tyreld You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=712784&aid=1203835&group_id=128809 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: sfcb Group: Usability Status: Open Resolution: None Priority: 5 Submitted By: Renier Morales (renierm) Assigned to: Adrian Schuur (a3schuur) Summary: make fails on yacc command Initial Comment: metaxa sfcb $ make yacc -p sfcQuery -d -o queryParser.c queryParser.y usage: yacc [-dlrtv] [-b file_prefix] [-p symbol_prefix] filename make: *** [queryParser.c] Error 1 ----------------------- Above is the error message I get. If I check the man page for yacc, I see there is no -o option for it. I am using yacc-1.9.1 from ftp://metalab.unc.edu/pub/Linux/devel/compiler-tools/ As I understand it, the -o option exists in byacc. If byacc was the yacc meant to be used with sfcb, then it should be a required dependency. I wonder if yacc in general is a dependency in sfcb at all. ---------------------------------------------------------------------- Comment By: Tyrel Datwyler (tyreld) Date: 2005-08-29 16:45 Message: Logged In: YES user_id=640104 Renier, The recently updated README reflects the fact that bison is a build requirement. Please close this defect. Thanks, Tyrel ---------------------------------------------------------------------- Comment By: Tyrel Datwyler (tyreld) Date: 2005-08-25 14:26 Message: Logged In: YES user_id=640104 On closer inspection of the parser code it has come to my attention that there are bison specific declarations present. We have thus come full circle and must require bison as a build requirement. [side note] Inspection of the gentoo yacc package shows that it is the yacc-1.9.1 code from metalab.unc.edu. As I pointed out earlier this *not* AT&T yacc but an old byacc implementation (look at the README). Further, this old code base has not been touched since 1997. The maintained byacc package has been updated to be ANSI C compliant as well as performance tuned. Further, it meets the POSIX standard for yacc compatablility. ---------------------------------------------------------------------- Comment By: Renier Morales (renierm) Date: 2005-08-24 10:45 Message: Logged In: YES user_id=660960 I think the fix for this bug is what tyreld recommended earlier, which is to require bison as a build requirement, or change the build to use only yacc comabatible options Gentoo has a yacc package for yacc, and a bison package for bison and a byacc package for byacc. It makes sense that if byacc is what is expected to exist, then to require this, since yacc still exist as yacc in other distributions. ---------------------------------------------------------------------- Comment By: Tyrel Datwyler (tyreld) Date: 2005-08-24 10:14 Message: Logged In: YES user_id=640104 I recommend this defect be closed. Any modern Linux distrobution provides either byacc or bison as the yacc implemenation they ship with. Both of which support the -o option (byacc namely does so in current implementations). Futher, it is highly unlikely to find anyone using the original AT&T implemenation of yacc as both byacc and bison have proved themselves as better alternatives, and the fact that an original AT&T implementation proves difficult to come by. ---------------------------------------------------------------------- Comment By: Tyrel Datwyler (tyreld) Date: 2005-08-24 09:40 Message: Logged In: YES user_id=640104 Renier, The yacc package you are using is actually a very old version, from around 1997, of byacc. New versions (the latest being 1.9 20050813) support the -o flag. ---------------------------------------------------------------------- Comment By: Tyrel Datwyler (tyreld) Date: 2005-08-08 10:57 Message: Logged In: YES user_id=640104 The -o option is a bison flag which is not compatible with yacc. Most systems use bison in place of yacc, and often replace yacc with a script that redirects execution to bison since bison recognizes all yacc options. We either need to explicitly require bison as a build requirement, or change the build to use only yacc comabatible options. ---------------------------------------------------------------------- Comment By: Renier Morales (renierm) Date: 2005-06-13 09:23 Message: Logged In: YES user_id=660960 I am using yacc-1.9.1 from ftp://metalab.unc.edu/pub/Linux/devel/compiler-tools/ ---------------------------------------------------------------------- Comment By: Adrian Schuur (a3schuur) Date: 2005-05-30 08:58 Message: Logged In: YES user_id=230251 What is the yacc version you are using ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=712784&aid=1203835&group_id=128809 |