Results 1 to 5 of 5
I'm getting a very weird error when compiling X from CVS... I never had something like this before. Have anyone of you compiled X from CVS in the last couple ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 08-18-2005 #1Just Joined!
- Join Date
- Oct 2004
- Posts
- 15
Error while compiling X from CVS
I'm getting a very weird error when compiling X from CVS... I never had something like this before. Have anyone of you compiled X from CVS in the last couple of days? Have you had issues with something like yylen, yylex, lex.o, and twm?
But if you have time to waste... please try to compile X from CVS
Here is the output with most of the errors:
Does anyone know what the matter is? I compiled recently from CVS and everything went fine. But I recompiled it (to follow this one procedure I received) and this comes up. Anyone have any idea? I know that a problem like this showed up way back in 2003 to someone else, but why now and why is it occurring?Code:... sed 's/ /./g'`\"" -DXVENDORNAME='"The X.Org Foundation"' -DXVENDORNAMESHORT='"X.Org"' -c -o lex.o lex.c lex.l:71: warning: redundant redeclaration of `yylineno' in same scope <stdout>:348: warning: previous declaration of `yylineno' <stdout>:724: warning: redundant redeclaration of `yylex' in same scope twm.h:412: warning: previous declaration of `yylex' <stdout>: In function `yylex': <stdout>:837: error: `yy_prev_more_offset' undeclared (first use in this function) <stdout>:837: error: (Each undeclared identifier is reported only once <stdout>:837: error: for each function it appears in.) <stdout>:821: warning: label `find_rule' defined but not used <stdout>: At top level: <stdout>:1482: warning: redundant redeclaration of `isatty' in same scope /usr/include/unistd.h:717: warning: previous declaration of `isatty' <stdout>:1753: warning: no previous prototype for `yyget_lineno' <stdout>:1762: warning: no previous prototype for `yyget_in' <stdout>:1770: warning: no previous prototype for `yyget_out' <stdout>:1778: warning: no previous prototype for `yyget_leng' <stdout>:1787: warning: no previous prototype for `yyget_text' <stdout>:1796: warning: no previous prototype for `yyset_lineno' <stdout>:1808: warning: no previous prototype for `yyset_in' <stdout>:1813: warning: no previous prototype for `yyset_out' <stdout>:1818: warning: no previous prototype for `yyget_debug' <stdout>:1823: warning: no previous prototype for `yyset_debug' <stdout>:1829: warning: no previous prototype for `yylex_destroy' <stdout>:1252: warning: `yyunput' defined but not used <stdout>:1862: warning: `yy_flex_strlen' defined but not used make[4]: *** [lex.o] Error 1 make[4]: Leaving directory `/usr/src/xc/programs/twm' make[3]: *** [all] Error 2 make[3]: Leaving directory `/usr/src/xc/programs' make[2]: *** [all] Error 2 make[2]: Leaving directory `/usr/src/xc' make[1]: *** [World] Error 2 make[1]: Leaving directory `/usr/src/xc' make: *** [World] Error 2 root@xandrames:/usr/src/xc#
- 08-19-2005 #2Linux Engineer
- Join Date
- Jan 2005
- Location
- Chicago (USA)
- Posts
- 1,028
Why are you compiling X from CVS?
- 08-19-2005 #3
Don't use CVS builds for important stuff. There is no guarantee that the code is stable at all.
I'd recommend grabbing the latest stable source release and compiling from that.
But aye, why DO you want to compile it from source?
- 08-23-2005 #4Just Joined!
- Join Date
- Oct 2004
- Posts
- 15
I need to use r300 drivers. The CVS X is the only server capable of recognizing it. Thus the CVS X is essential.
- 08-23-2005 #5Linux Newbie
- Join Date
- Nov 2004
- Location
- New York
- Posts
- 150
I'm no expert on CVS or X, so all I can give is general advice. Make sure you're looking at the first error message that appears (you can probably neglect warnings). Pay special attention to anything about missing include files, and during the final linking stage, missing libraries. They are indicators that you may not have installed some required devel packages, and can easily result in hundreds of reported errors per file. Also if a symbol is not declared, it may just be that its name has changed since the last time you updated your libraries. Although since this is CVS I think it's a lot more likely that some developer simply screwed up.
If you're really desperate, check to make sure that the latest source release compiles on your machine, and then... I guess find the developer forum for X. Good luck.
\"Nifty News Fifty: When news breaks, we give you the pieces.\" - Sluggy Freelance


Reply With Quote
