frank at g-n-u.de
Sat Jan 13 10:48:48 CET 2001
Kocherlakota Harikrishna wrote:
> Thanks again for your help. Infact we emptied all the directories and built the
> compiler fresh from the tar files. Eventhen we got the same compilation problems.
> Then we compiled with -v option and are unable to find any clue. Herewith we are
> attaching the verbose ouput for U to have a look.
The output is very hard to read because it has wrong/mostly missing
line breaks. The verbose output usually is convoluted enough
already, but this one is really like a labyrinth. ;-) Could you
please send it again with proper line breaks? (Try redirecting it to
a file using `>& file name', and possibly include the file as in
MIME base 64 if thing went wrong there...)
Also, could you please give us some information about the unit
structure of your project? I assume pcamac.pas contains the main
program, right? Are pekxac.pas pguzaa.pas units? Which units (of
yours and from GPC) does each file use, and are the `uses'
statements in the interface or implementation?
Just to be sure: You're not using a symbol `_p_strrscan' in your own
code or have copied a declaration from gpc.pas, are you? That would
be likely to cause such problems. (In general, all names starting
with `_p_' are reserved by GPC and should not be used in normal
Frank Heckenbach, frank at g-n-u.de, http://fjf.gnu.de/
GPC To-Do list, latest features, fixed bugs:
More information about the Gpc