| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 <2006> 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 <2006> 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | antelope errors |
| From: | "Al Honey" <[email protected]> |
| To: | <[email protected]> |
| Date: | Wed, 22 Mar 2006 11:24:10 -1000 |
|
Aloha
This is more ignorance on my part. Do I need to track down the cause of the warnings in the input file or do I ignore these as there is a function call to remove_conflicts() (i.e. does that function fix things or delete the stuff that was found to be errant from the output?)? If the input file needs to be fixed is there a mechanism for enabling more error message so as to find the lines in question?
/usr/local/epics/r3.13.10/base/bin/solaris/antelope -t ../pvload.y /usr/local/epics/r3.13.10/base/bin/solaris/antelope: 4 shift/reduce conflicts, 5 reduce/reduce conflicts. mv y.tab.c pvload.c
Thanks for any help
AH
|