• State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 22 subscribers
  • Views 1347 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Compile problem

Zohar Mann

I am compiling a file using the c51
Compiler. It seems that c51 is doing something but there is not any output,
no message, nothing. Further more if
I made by intension some syntax error the compiler produces the .lst file and
the compiler banner output is seen on the DOS window. Other files are compiled OK

The compiler is version V5.02

Parents
  • 0

    Are you saying it's just one particular 'C' source file which gives you this problem?
    Is there anything special about it:
    - very big?
    - very small?
    - lots of includes?

    How are you running the compiler:
    - command line?
    - make?
    - uVision?
    - other "IDE?"

    What OS version(s)?

    What do you get in the .lst file?

    Have you accidentally chosen (a) file name(s) which is (are) "reserved;" eg,
    PRN
    AUX
    CON

Reply
  • 0

    Are you saying it's just one particular 'C' source file which gives you this problem?
    Is there anything special about it:
    - very big?
    - very small?
    - lots of includes?

    How are you running the compiler:
    - command line?
    - make?
    - uVision?
    - other "IDE?"

    What OS version(s)?

    What do you get in the .lst file?

    Have you accidentally chosen (a) file name(s) which is (are) "reserved;" eg,
    PRN
    AUX
    CON

Children
  • 0 in reply to Andrew Neil


    It happens both from a command line or the CodeWright IDE.It is a large file, but larger files could be compiled. It has include files but no more than other files which can be compiled


    The OS is windows NT2000


    I do not get any .lst file.

    I did not chose any "reserved;" file name.


  • 0 in reply to Zohar Mann

    First you wrote:
    "...Further more if I made by intension some syntax error the compiler produces the .lst file and the compiler banner output is seen on the DOS window..." (my emphasis)

    But then you said,
    "I do not get any .lst file."

    So which is it?

    "The OS is windows NT2000"
    Do you mean Windows-NT, or Windows-2000?

  • 0 in reply to Andrew Neil

    Yes it is windows NT.

    If the file is OK i.e. not syntax errors or other compilation errors the compiler does not produce a .lst file
    and it does not output anything to the
    command window. But if I make a syntax error somewhere in the file the .lst file is produced and the compiler send
    a message to the DOS window from where
    I am activating the command line

  • 0 in reply to Zohar Mann

    So, when you do get a .lst file, What do you get in the .lst file?
    Are there any other errors or warnings?
    Especially if you make your deliberate mistake right near the end of the file.

    Have you tried looking at the preprocessor output?

    Do you have another compiler you could try?

  • 0 in reply to Andrew Neil

    Hi

    I found the problem. It was a code line that exceeds the maximal length per one code line.

    I have a #define with many lines that were concatenated with the "\ " and this makes the long line.

    Thanks for the help

    Zohar