Hi,
There is indeed an option, available in the C++ product, to ignore some link errors. This option is -no-extern-C.
This option is present in the C++ product because some functions may be declared inside an extern “C” { } block in some files and not in others. Then, their linkage is not the same and it causes a link error, according to the ANSI standard.
Those link errors can then be bypassed by using this option, but the goal is not to bypass all link errors. When you have other kinds of link errors in C++ or in C, they have to be fixed, as the message said. They are indeed real problems in the code.
Typically, a link error occurs when you have something like:
one_file.c:
int x;
another_file.c:
float x;
As you can imagine, Polyspace cannot prove anything on x if its type is not clearly defined. There is something wrong in the definition of x, that needs to be fixed. Consider the link errors given by Polyspace Code Prover as bugs.
By the way, Polyspace Bug Finder provide a specific defect for this link errors: DECLARATION_MISMATCH.
Alex
