On Wed, 31 Jan 2007 10:19:06 -0800, Rick Jones <rick.jones2@hp.com> wrote:

> breyfogle <breyfogle@aol.com> wrote:
>
> [ trim, please ]
>
>> ...Made a bit of progress by building a simplier package (enscript)
>> that does similar things. I can get enscript build with only the
>> following warning messages. Something is not right WRT lex (I
>> think). Although the enscript build completes, when it is run, I
>> can get fatal run-time errors about these same undefined symbols.
>> Any Ideas ?
>
>> cc -g -o states main.o utils.o prims.o process.o gram.o lex.o
>> ../afmlib/libafm.a ../compat/libcompat.a -ll
>
>> ld: (Warning) Unsatisfied symbol "yylenguc" in file
>> /usr/lib/hpux32/libl.so
>> ld: (Warning) Unsatisfied symbol "yyinput" in file
>> /usr/lib/hpux32/libl.so
>> ld: (Warning) Unsatisfied symbol "yyunput" in file
>> /usr/lib/hpux32/libl.so
>> ld: (Warning) Unsatisfied symbol "yyolsp" in file
>> /usr/lib/hpux32/libl.so
>> ld: (Warning) Unsatisfied symbol "yyoutput" in file
>> /usr/lib/hpux32/libl.so
>> ld: (Warning) Unsatisfied symbol "yytextuc" in file
>> /usr/lib/hpux32/libl.so
>> ld: (Warning) Unsatisfied symbol "yyextra" in file
>> /usr/lib/hpux32/libl.so
>> ld: (Warning) Unsatisfied symbol "yyfnd" in file /usr/lib/hpux32/libl.so
>> ld: (Warning) Unsatisfied symbol "yyprevious" in file
>> /usr/lib/hpux32/libl.so
>> ld: (Warning) Unsatisfied symbol "yylsp" in file /usr/lib/hpux32/libl.so
>> ld: (Warning) Unsatisfied symbol "yylstate" in file
>> /usr/lib/hpux32/libl.so
>> ld: (Warning) Unsatisfied symbol "yytextarr" in file
>> /usr/lib/hpux32/libl.so
>> ld: (Warning) Unsatisfied symbol "yyback" in file
>> /usr/lib/hpux32/libl.so
>> 13 warnings.
>
>
> Being woefully ilinfomred about lex (flex) and yacc (bison), I'd be
> inclined to think that indeed, something was amis - the build did
> indeed use HP's lex and not a flex you installed?
>
> Was there any use of yacc? ISTR that "yy" routines may be yacc
> routines - perhaps a -ly is needed as well?
>
> rick jones

There is actually quite an extensive e-trail for this same problem dating
back several years that seems to implicate something about HP's ia64 lex
implementation. One thread I found was typical:

http://sources.redhat.com/ml/binutil.../msg00337.html

Unfortunately, I have not found any hint of a solution. Building GNU flex
might work but that also requires GNU Bison and maybe gcc, gmake etc....

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/