Solved my problem - I deleted the line with the offending
#endif and re-added it.  Then it compiled.

Phil
> That worked, Simon.  Thanks.  For the archives, here is
> what I put in my environment variable INCLUDE:
>
> 
>/QIBM/ProdData/ILEC:/QIBM/ProdData/ILEC/include:/QIBM/include:/home/phil/apps/in
> clude
>
> Now I am getting a parsing error.  There is an #endif
> that is getting copied as #endi.
>
> Here's part of the compile listing:
>
>    61       |FM_IMPORT void fmRemoveLListItem(fmLList*
> List,fmLListNode* Node);                                |
>   3427     1
>    61       + void fmRemoveLListItem(fmLList*
> List,fmLListNode* Node);
>         +   3427     1
>    62       |
>                                                       |
>  3428     1
>    63       |#endi
>                                                       |
>  3429     1
> ===========>
> 
>.a..............................................................................
> ..................
> *=Warning=========> a - CZM0430 The preprocessing
> directive endi is not valid.
>
> But the relevant source code snip looks like this:
>
> FM_IMPORT void fmRemoveLListItem(fmLList*
> List,fmLListNode* Node);
>
>
> #endif
>
>  ************End of Data********************
>
>
> Is this a known problem?  Should I call IBM about this?
>
> Thanks,
>
> Phil
> _______________________________________________
> This is the C programming iSeries / AS400 (C400-L) mailing list
> To post a message email: C400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/c400-l
> or email: C400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/c400-l.
>


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].