preface: i do not /know/ C but have been able to wheedle my
way thru some problems in the past and even create a few very
minor programs... i can only point out what i see and ask
questions or just wait for a solution...
in the sqafix sources retrieved from cvs.sourceforge.net, i
get the following errors...
preface: i do not /know/ C but have been able to wheedle my way thru
some problems in the past and even create a few very minor programs...
i can only point out what i see and ask questions or just wait for a solution...
in the sqafix sources retrieved from cvs.sourceforge.net, i get the following errors...
=====
In file included from dw-def.h:34,
from dw-lst.h:35,
from sqafix.h:63,
from sqafix.c:62:
dw-saa.h:297: parse error before string constant
dw-saa.h:297: stray '\' in program
dw-saa.h:298: undefined or invalid # directive
=====
here're the lines in that section with line numbers added..
293 #ifdef NDEBUG
294 # define ASSERT(p) ((void)0)
295 #else
296 # define ASSERT(p) ((p) ? (void)0 : (void) fprintf(stderr, \
297 "Assertion failed: %s, file %s, line %d\n\a",
\
298 #p, __FILE__, __LINE__ ) )
299 #endif
i'm not sure i see the two afore mentioned problems...
=====
In file included from dw-lst.h:35,
from sqafix.h:63,
from sqafix.c:62:
dw-def.h:140: parse error before `USHORT'
dw-def.h:173: parse error before string constant
dw-def.h:173: stray '\' in program
dw-def.h:174: undefined or invalid # directive
=====
line 140 is...
(USHORT)0x0F00)
and in comparison with other lines containing USHORT in that
area, it is possible that it should read
((USHORT)0x0F00)
[this one i believe i have fixed as it hasn't shown up in subsequent compile attempts...]
here're the lines in section 173/174 with line numbers added..The problem -----^
169 #ifdef NDEBUG
170 # define ASSERT(p) ((void)0)
171 #else
172 # define ASSERT(p) ((p) ? (void)0 : (void) AuxLog( \
173 "Assertion failed: %s, file %s, line %d", \
174 #p, __FILE__, __LINE__ ) )
175 #endif
this section is almost identicle to the one in dw-saa.h and the error
must be something similar if not the very same...
=====
In file included fron sqafix.c:62:
sqafix.h:261: undefined or invalid # directive
=====
here're the lines in that section with line numbers added..
257 #ifdef NDEBUG
258 # define ASSERT(p) ((void)0)
259 #else
260 # define ASSERT(p) ((p) ? (void)0 : (void) Assert( \
261 #p, __FILE__, __LINE__ ) )
262 #endif
this section is almost identicle to the one in dw-saa.h and
dw-def.h... the error must be something similar if not the very same
as the other two...
in all three, i'm wanting to question, at least, the #p on the last line... i have no idea on the "parse error before string constant" errors...
i believe that once these few problems are handled, i'll be able to conpile sqafix and thus complete a "make build" of a new install of
the maximus cvs tree...
function `DoFormatMSGID':
sqamsg.c:126: `timer_t' undeclared (first
use in this function)
sqamsg.c:126: (Each undeclared identifier is
reported only once
sqamsg.c:126: for each function it appears
in.) sqamsg.c:126: parse error before `t' sqamsg.c:156: `t'
undeclared
293 #ifdef NDEBUG
294 # define ASSERT(p) ((void)0)
295 #else
296 # define ASSERT(p) ((p) ? (void)0 : (void) fprintf(stderr, \
297 "Assertion failed: %s, file %s, line %d\n\a",
\
298 #p, __FILE__, __LINE__ ) )
299 #endif
Hmmm.. I can't understand why my gcc didn't fault on that one!
Try to do a CVS checkout.
((USHORT)0x0F00)
No, the count of ( match the count of ), just the problem
about \ in defines.
here're the lines in section 173/174 with line numbers added..
169 #ifdef NDEBUGThe problem -----^
170 # define ASSERT(p) ((void)0)
171 #else
172 # define ASSERT(p) ((p) ? (void)0 : (void) AuxLog( \
173 "Assertion failed: %s, file %s, line %d", \
174 #p, __FILE__, __LINE__ ) )
175 #endif
What version of gcc do you use?
function `DoFormatMSGID':
sqamsg.c:126: `timer_t' undeclared (first
use in this function)
sqamsg.c:126: (Each undeclared identifier is
reported only once
sqamsg.c:126: for each function it appears
in.) sqamsg.c:126: parse error before `t' sqamsg.c:156: `t'
undeclared
It's fixed, should be time_t, damn I don't understand why my
version is working!!
Hmmm.. I can't understand why my gcc didn't fault on that one!
what did you see other than the \'s on 296 and 297? what other error
is in there?
Try to do a CVS checkout.
that's how i got what i have now... i've about taken to blowing the
whole tree and starting from scratch each time i retrieve the stuff
from cvs...
((USHORT)0x0F00)
No, the count of ( match the count of ), just the problem
about \ in defines.
right, i figured that out later...
here're the lines in section 173/174 with line numbers added..
169 #ifdef NDEBUG
170 # define ASSERT(p) ((void)0)
171 #else
172 # define ASSERT(p) ((p) ? (void)0 : (void) AuxLog( \
The problem -----^
yup... in all three of those, from what i see...
173 "Assertion failed: %s, file %s, line
%d", \ 174 #p, __FILE__, __LINE__ ) ) 175
#endif
[trim]
What version of gcc do you use?
2.95.3 on mandrake 7.1 (helium)...
It's fixed, should be time_t, damn I don't understand why my
version is working!!
ok, i'll try another cvs retrieval and build... should only take 20 or
30 minutes or so... that is, if cvs is open and lets me in ;-)
It's fixed, should be time_t, damn I don't understand why my
version is working!!
ok, i'll try another cvs retrieval and build... should only take 20 or
30 minutes or so... that is, if cvs is open and lets me in ;-)
It should be.. I don't know if sourceforge still have CVS
problems..
It's fixed, should be time_t, damn I don't understand why my
version is working!!
ok, i'll try another cvs retrieval and build... should only take
20 or 30 minutes or so... that is, if cvs is open and lets me in
;-)
It should be.. I don't know if sourceforge still have CVS
problems..
it got further... sqastr.c is full of \'s too ;-(
it got further... sqastr.c is full of \'s too ;-(
I _really_ don't understand it.. You're scure of there ain't
Carrige Return in the source file?
it got further... sqastr.c is full of \'s too ;-(
I _really_ don't understand it.. You're scure of there ain't
Carrige Return in the source file?
i haven't looked... the files are straight off sourceforge... the
linux box goes and grabs them and haves at them... i don't pull
anything *nix oriented on anything other than a *nix box unless i'm
going to try to compile it with EMX on OS2 and see if it works...
it got further... sqastr.c is full of \'s too ;-(
I _really_ don't understand it.. You're scure of there ain't
Carrige Return in the source file?
i haven't looked... the files are straight off sourceforge... the
linux box goes and grabs them and haves at them... i don't pull
anything *nix oriented on anything other than a *nix box unless i'm
going to try to compile it with EMX on OS2 and see if it works...
Very good, I would presuiate if you gave me a compile log too,
because I doubt that we/I did remember #ifdef UNIX every
place.
i haven't looked... the files are straight off sourceforge... the
linux box goes and grabs them and haves at them... i don't pull
anything *nix oriented on anything other than a *nix box unless i'm
going to try to compile it with EMX on OS2 and see if it works...
Very good, I would presuiate if you gave me a compile log too,
because I doubt that we/I did remember #ifdef UNIX every
place.
i'm starting it all again, right now at the timestamp on this
message... just deleted the maximus directory and unzippes the max-3.03-etc.tar.gz file and now my script is pulling it all from cvs again...
i'm starting it all again, right now at the timestamp on this
message... just deleted the maximus directory and unzippes the
max-3.03-etc.tar.gz file and now my script is pulling it all from cvs
again...
Okay. A checkout should do it :-)
i'm starting it all again, right now at the timestamp on this
message... just deleted the maximus directory and unzippes the
max-3.03-etc.tar.gz file and now my script is pulling it all from
cvs again...
Okay. A checkout should do it :-)
had to do a bit of surgery on sqastr.c and sqaexe.c...
tr "\015" "\040" < sqastr.c > sqastr.c2
mv sqastr.c sqastr.c1
mv sqastr.c2 sqastr.c
tr "\015" "\040" < sqaexe.c > sqaexe.c2
mv sqaexe.c sqaexe.c1
mv sqaexe.c2 sqaexe.c
then sqastr.c required additional editing to recombine the lines continued by \ on the end of them...
after doing that, i'm am apparently getting a complete compile
process as my maxbuild.log file is now ending with..
Build Complete; edit your control files and 'make install'
i can't tell you what lines contain the ^M in those two source files
as i was unable to get grep to look for that character... and i have
no idea about the \ continuation lines problem... is there some
setting for gcc or something that i may be able to look at and
adjust??
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,090 |
Nodes: | 15 (0 / 15) |
Uptime: | 38:14:47 |
Calls: | 232,706 |
Calls today: | 1 |
Files: | 60,048 |
D/L today: |
29 files (144M bytes) |
Messages: | 298,958 |