Menu
▾
▴
Re: [htdig-dev] conf_parser.cxx:340: error: `aConf' undeclared (first use this function)
|
From: Neal R. <ne...@ri...> - 2004-11-05 20:33:24
|
Simon,
Please look at the header for the attached file conf_parser.cxx
[nealr@yellowstone SF-CVS-linux-gcc3.2]$ head ~/conf_parser.cxx
#ifndef lint
/*static char yysccsid[] = "from: @(#)yaccpar 1.9 (Berkeley)
02/21/93";*/
static char yyrcsid[] = "$Id: skeleton.c,v 1.4 1993/12/21 18:45:32 jtc Exp
$";
#endif
#define YYBYACC 1
#define YYMAJOR 1
#define YYMINOR 9
#define yyclearin (yychar=(-1))
#define yyerrok (yyerrflag=0)
#define YYRECOVERING (yyerrflag!=0)
Here is the 'head' of my file:
[nealr@yellowstone SF-CVS-linux-gcc3.2]$ head htcommon/conf_parser.cxx
/* A Bison parser, made from
/home/hutchisn/src/htdig/htcommon/conf_parser.yxx
by GNU Bison version 1.28 */
#define YYBISON 1 /* Identify Bison output. */
>I just tried to compile htdig from CVS (23rd Oct 2004) on Suse 9.1.
>Initially I didn't have yacc installed
>so it failed but now I have installed yacc (version 91.7.30-768 from Suse
>9.0, no 9.1 version available) and also bison rpms (version 1.875).
Note that it appears that your makefile is not actually using the version
of bison on your machine.. it's using yacc which from the above message
and the header appears to be a 10 year old version of Berkeley YACC.
The issue is likely caused by some 'Bison-isms' we have in the
conf_parser.yxx file that make it incompatible with Berkeley YACC
resulting in an uncompilable file.
Edit your makefiles and specifiy that they use 'bison'.
Thanks
On Thu, 4 Nov 2004, Simon Blandford wrote:
> Hi Neal,
>
> Appologies for not reading the email properly :-[
>
> Gzipped up conf_parser.cxx is attached.
>
> Thanks,
> SimonB
>
> Neal Richter wrote:
>
>>
>> Please respond with the conf_parser.cxx attached after bison runs on
>> conf_parser.lxx
>>
>> Thanks!
>>
>> On Mon, 1 Nov 2004, Simon Blandford wrote:
>>
>>> Hi Neal,
>>>
>>> Bison/yacc version is...
>>>
>>> simon@suse:~> bison -V
>>> bison (GNU Bison) 1.875
>>>
>>> Regards,
>>> SimonB
>>>
>>> Neal Richter wrote:
>>>
>>>>
>>>> Could you reply with your exact version of bison/yacc?
>>>>
>>>> Also send the conf_parser.cxx file after running bison on it.
>>>>
>>>> Thanks
>>>>
>>>> On Sat, 23 Oct 2004, Simon Blandford wrote:
>>>>
>>>>> I just tried to compile htdig from CVS (23rd Oct 2004) on Suse 9.1.
>>>>> Initially I didn't have yacc installed so it failed but now I have
>>>>> installed yacc (version 91.7.30-768 from Suse 9.0, no 9.1 version
>>>>> available) and also bison rpms (version 1.875).
>>>>>
>>>>>
>>>>> Now I get the following error...
>>>>>
>>>>> conf_parser.cxx: In function `int yyparse()':
>>>>> conf_parser.cxx:340: error: `aConf' undeclared (first use this function)
>>>>> conf_parser.cxx:340: error: (Each undeclared identifier is reported only
>>>>> once
>>>>> for each function it appears in.)
>>>>> conf_parser.cxx:271: warning: label `yyerrlab' defined but not used
>>>>> /usr/include/g++/iostream: At top level:
>>>>> conf_parser.cxx:3: warning: `char yyrcsid[52]' defined but not used
>>>>> make[1]: *** [conf_parser.lo] Error 1
>>>>> make[1]: Leaving directory `/mnt/data/local/src/htdig/htcommon'
>>>>> make: *** [all-recursive] Error 1
>>>>>
>>>>>
>>>>>
>>>>> If I grep the config.log file I see that bison is detected...
>>>>>
>>>>> simon@suse:/usr/local/src/htdig> grep "bison" config.log
>>>>> configure:4198: checking for bison
>>>>> configure:4214: found /usr/bin/bison
>>>>> configure:4224: result: bison -y
>>>>> ac_cv_prog_YACC='bison -y'
>>>>> YACC='bison -y'
>>>>>
>>>>>
>>>>> If I grep for aconf, the function that seems to be causing all the
>>>>> tears, I get...
>>>>> simon@suse:/usr/local/src/htdig> grep -i "aconf" * -R
>>>>> htcommon/conf_parser.cxx:#define YYPARSE_PARAM aConf
>>>>> htcommon/conf_parser.cxx: ((HtConfiguration
>>>>> *)aConf)->AddParsed(yyvsp[0].ConfLine->name,yyvsp[0].ConfLine->value);
>>>>> htcommon/conf_parser.cxx: ((HtConfiguration
>>>>> *)aConf)->Add(yyvsp[-10].str,yyvsp[-8].str,yyvsp[-5].ConfLines);
>>>>> htcommon/conf_parser.yxx:#define YYPARSE_PARAM aConf
>>>>> htcommon/conf_parser.yxx: ((HtConfiguration
>>>>> *)aConf)->AddParsed($1->name,$1->value);
>>>>> htcommon/conf_parser.yxx: ((HtConfiguration
>>>>> *)aConf)->Add($2,$4,$7);
>>>>>
>>>>>
>>>>> The only other case I can find of this error was from the dev mailing
>>>>> list back in April...
>>>>> http://sourceforge.net/mailarchive/message.php?msg_id=8195355
>>>>> It appears that when Joe tried the following (for me it is
>>>>> /usr/bin/bison) and it worked for him...
>>>>> gmake distclean
>>>>> YACC="/usr/local/bin/bison"
>>>>> export YACC
>>>>> ./configure
>>>>> gmake
>>>>> ...but it made no difference for me :-( even using "export
>>>>> YACC="/usr/bin/bison -y" as later suggested by Gilles.
>>>>>
>>>>>
>>>>> Any help on solving this puzzle would be appreciated.
>>>>> Thanks,
>>>>> SimonB
>>>>>
>>>>>
>>>>>
>>>>> -------------------------------------------------------
>>>>> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
>>>>> Use IT products in your business? Tell us what you think of them. Give
>>>>> us
>>>>> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out
>>>>> more
>>>>> http://productguide.itmanagersjournal.com/guidepromo.tmpl
>>>>> _______________________________________________
>>>>> ht://Dig Developer mailing list:
>>>>> htd...@li...
>>>>> List information (subscribe/unsubscribe, etc.)
>>>>> https://lists.sourceforge.net/lists/listinfo/htdig-dev
>>>>>
>>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by:
>>> Sybase ASE Linux Express Edition - download now for FREE
>>> LinuxWorld Reader's Choice Award Winner for best database on Linux.
>>> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
>>> _______________________________________________
>>> ht://Dig Developer mailing list:
>>> htd...@li...
>>> List information (subscribe/unsubscribe, etc.)
>>> https://lists.sourceforge.net/lists/listinfo/htdig-dev
>>>
>>
>
>
>
--
Neal Richter
Knowledgebase Developer
RightNow Technologies, Inc.
Customer Service for Every Web Site
Office: 406-522-1485
|
