Pro * C - Error 4033: Missing #Endif at End of File.

[edmilton]

Hi, Folks!

I have got the following Message When Building to PRO * C PROG PROGMENT:


The problem is the code doesn 'There was an open #ifdef or #ifndef Directives.

I'vê Found A Comment on this Message On Google Stating That The Back Slash Can Cause Such Error So I'vê Striped All Back Slashes OUT FROM THE CODE BUT THE ERROR REMAINS.

I Will Appreciate Any Help on this Issue.

Thanks to Lot.

Edi

[SergioLBJr]

Face two things

Post your code for us to take a look.

If you post in Portuguese the probability of someone giving you a force will be greater.

[victorhugomuniz]

Select all

 
The following macros provide ways to find and exercise a C Compiler. There are a few constructs that ought to be avoided, but do not deserve being checked for, since they can easily be worked around. 
 
Don't use lines containing solitary backslashes 
    They tickle a bug in the HP-UX C compiler (checked on HP-UX 10.20, 11.00, and 11i). Running the compiler on the following source, 
 
     	 
 
    #ifdef __STDC__ 
    /\ 
    * A comment with backslash-newlines in it. %{ %} *\ 
    \ 
    / 
    char str[] = "\\ 
    " A string with backslash-newlines in it %{ %} \\ 
    ""; 
    char apostrophe = '\\ 
    \ 
    '\ 
    '; 
    #endif 
 
    yields 
 
     	 
 
    error-->cpp: "foo.c", line 13: error 4048: Non-terminating comment at end of file. 
    error-->cpp: "foo.c", line 13: error 4033: Missing #endif at end of file. 
 
    Removing the lines with solitary backslashes solves the problem. 
 
Don't compile several files at once if output matters to you 
    Some compilers, such as the HP's, reports the name of the file it is compiling when they are several. For instance:  

[url=http://www.delorie.com/gnu/docs/autocon ... nf_64.html]fonte

Please use portugues here in the forum

[edmilton]

Gee, guys! It went badly!

Sergio talked about posting in Portuguese and I was shocked: Shock :. Believe that I was seeing the whole site in English ? I did not even realize that I was in Portuguese: LOL:!

Then beleza!

I have already solved the previous problem. Now, I'm beating myself with the following message:

Select all

cc: warning 485: Can't open "dsn_esninv.c".

The code errors have already been fixed but I can not go ahead because of this error.

Thanks for the Help.

Edi

[victorhugomuniz]

[url=http://forums13.itrc.hp.com/service/for ... Id=1092969]ajuda

[edmilton]

Victor,

I had already seen this forum. In fact, the problem is that Precessor Pro * C is not generating .c from .PPC. That is why CC is print this message. Pro * C is generating a core name file, which gives no information to find out what is happening and the .lis is empty.