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
--
The computing industry isn't as much a game of "Follow The Leader" as
it is one of "Ring Around the Rosy" or perhaps "Duck Duck Goose."
- Rick Jones
these opinions are mine, all mine; HP might not want them anyway...
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...