Compiler error for missing include file is hard to interpret

David Aldrich92784

We are running CCS 5.3 and CGT 7.2.4. I frequently find that the compiler error output is difficult to interpret for the case where a header file is missing.

For example, consider the case where:

fileA.c includes fileB.h, which includes fileC.h, which includes (at line 24) fileD.h.

Suppose fileD.h is missing. The compiler reports:

--cmd_file="./configPkg/compiler.opt" "fileA.c"

"fileC.h", line 24: fatal error #5: could not open source file "fileD.h"

1 fatal error detected in the compilation of "fileA.c".

Compilation terminated.

So the problem is that the compiler makes no mention of fileB.h. I believe that gcc compilers do a much better job of this and would report each include file in the tree that the compiler traversed until it found an error.

Is there an option to improve the error reporting or is this a bug or limitation?

David

over 12 years ago

0 George Mock over 12 years ago

TI__Guru**** 251270 points

There is no build option or other mechanism to have the compiler report the chain of include files that leads to the error. The option --gen_acp_raw creates a fileA.rl file which helps, but isn't quite as friendly as what you suggest. You can read about it in the C6000 compiler manual.

Thanks and regards,

-George

0 David Aldrich92784 over 12 years ago in reply to George Mock

Genius 3720 points

Thanks. Please will you feedback my question to the compiler team for improvement of the tools?

David

0 George Mock over 12 years ago in reply to David Aldrich92784

TI__Guru**** 251270 points

I filed SDSCM00047209 in the SDOWP system to request this enhancement to compiler diagnostics. Feel free to follow it with the SDOWP link below in my signature.

Thanks and regards,

-George

Code Composer Studio™︎

Code Composer Studio forum

Compiler error for missing include file is hard to interpret