Mail Archives: djgpp/1998/10/15/00:16:36
George, this is the kind of frustration I suggested I may have to post as
well.
I've been progressing pretty well, writing Nasm code and linking with DJGPP.
I worked on a modestly sizeable Borland conversion project. After marching
through a huge page of compiler error messages(newbie dumb stuff), and
resolving one at a time I finally get down to a compiler execution line and
output that looks like this:
C:\Work\pcx >gcc pcxview3.cc pcx.o myscrn1.o myscrn2.cc -o pcxview.exe
pcxview3.cc:71: parse error at end of input.
Now my pcxview3.cc file has only 70 lines in it! What's also baffling is the
file pcx.o was compiled a couple of weeks ago, but now I can't compile it
again. I get the same kind of error message for the end of its 276 lines of
code.
I have assumed I'm missing a squiggly bracket or a semicolon or something,
but I'm going up a wall! I've brought the files into several editors and
made sure there is nothing like a non-printing character at the end. I've
flipped the order of functions in the source to make sure it is not specific
to one function at the end. The parse error always appears at one line past
the end of my code.
By the way, the things I've done above sometimes work, for others listening
in.
-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
- Raw text -