Daniel, I ran the debug you asked. When I ran less against the geo00.h.x0 file, I noticed that all the lines had MS CR-LF (^M) at the end. When I used sed to strip those off, and re-ran "imf.pl all" I got very different results (still not good results, but different!): # imf.pl all Create gsp100.h first: vmake 10.00.08 30-04-2002 VMAKE_PATH=/tmp/sapdbsrc, 28-05-02 12:55:43 start of collection phase 28-05-02 12:55:44 end of collection phase 28-05-02 12:55:44 start of gsp100.h fast gsp100.h missing command script 'mfcinc.pl' 28-05-02 12:55:44 end of gsp100.h fast Inconsistent build information between $RELVER(R74) and gsp100.h (R-1-1)
# find . -name gsp100.h -ls 208899 8 -r--r--r-- 1 500 513 8177 May 16 16:16 ./sys/src/sp/gsp100.h 19033 0 -rwxr-xr-x 1 root root 0 May 24 21:28 ./sys/wrk/incl/gsp100.h 19050 8 -rw-rw-r-- 1 root root 8177 May 16 16:16 ./sys/wrk/fast/tmp/gsp100.h Mark Post -----Original Message----- From: Dittmar, Daniel [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 28, 2002 8:22 AM To: 'Post, Mark K'; 'sapdb' Subject: RE: Source Build Error > After I build the tools, and try to compile the source, I get > this error: > > # imf.pl all > Create gsp100.h first: > vmake 10.00.08 30-04-2002 > VMAKE_PATH=/tmp/sapdbsrc, > 24-05-02 19:09:12 start of collection phase > ' unexpected x error in > '/tmp/sapdbsrc/sys/desc//SAPDB/RunTime.com' line 54: > 'else > ' unexpected x error in Please run 'imf.pl -D5 geo00.h'. This should emit lots of traces in addition to the error. You don't have to redirect the output, it can be found as $WRK/fast/prot/heo00.h.x0. The interesting part looks like this on my machine: fileopen: opened '<whatever>///sys/desc//SAPDB/RunTime.com' ... concom: line 50: &if $OS = WIN32 lex: called lex: got token 'if' allocate_token: called, tokenval 'if' allocate_token: allocated token 'if' lex: returning 261 'if' lex: called allocate_token: called, tokenval '$' allocate_token: allocated token '$' lex: returning 36 '$' lex: called lex: got token 'OS' allocate_token: called, tokenval 'OS' allocate_token: allocated token 'OS' lex: returning 269 'OS' ident 'OS' substitute 'OS' found 'OS' = 'UNIX' -> 'UNIX' lex: called allocate_token: called, tokenval '=' allocate_token: allocated token '=' lex: returning 287 '=' lex: called lex: got token 'WIN32' allocate_token: called, tokenval 'WIN32' allocate_token: allocated token 'WIN32' lex: returning 269 'WIN32' token like identifier 'WIN32' lex: called lex: got token '' lex: returning, no more tokens on line allocate_token: called, tokenval 'end-of-line' allocate_token: allocated token 'end-of-line' lex: returning 0 'end-of-line' eq 'UNIX' 'WIN32' -> '0' if '0' if: nesting_level 0 if: suppress[0] 0 if: suppress[1] 0 if: suppress 1 filegets: called filegets: returning filegets: called filegets: returning filegets: called filegets: returning filegets: called filegets: returning concom: line 54: &else lex: called lex: got token 'else' allocate_token: called, tokenval 'else' allocate_token: allocated token 'else' lex: returning 263 'else' lex: called lex: returning, ccp 0xbfffb779, lex_ignore 1 allocate_token: called, tokenval 'end-of-line' allocate_token: allocated token 'end-of-line' lex: returning 0 'end-of-line' else else: nesting_level 0 else: suppress[0] 0 else: suppress[1] 0 else: suppress 0 This basically means that the processor - detects that $OS is not WIN32 - switches suppress to true - skips a few lines - until &else is found Are there any major (or perhaps even minor) differences in your protocol? Daniel Dittmar -- Daniel Dittmar SAP DB, SAP Labs Berlin [EMAIL PROTECTED] http://www.sapdb.org/ _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
