diff -r 80ef3a206772 -r 48780e181b38 Symbian3/SDK/Source/GUID-0E3E2FAD-FC85-5995-8B5C-8F1C1A4186D0.dita --- a/Symbian3/SDK/Source/GUID-0E3E2FAD-FC85-5995-8B5C-8F1C1A4186D0.dita Fri Jul 16 17:23:46 2010 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,13 +0,0 @@ - - - - - -Troubleshooting Tips for RVCT v3.1

This section is intended to help you troubleshoot the errors that may occur after migrating to RealView Compilation Tools (RVCT) v3.1. It provides a list of common problems that you may face while building your component using RVCT v3.1, with possible causes and ways to troubleshoot the problems.

Problem Possible cause Possible solution

Error: L6410W: Symbol <symbol_name > with non STV_DEFAULT visibility STV_HIDDEN should be resolved statically, cannot use definition in <dso_file_name >

The linker is aware that the symbol (function) is present in another DLL, but in at least one of the source files of your component the symbol (function) has been declared without the IMPORT_C modifier.

Identify such source files and prefix the symbol declaration with the IMPORT_C modifier.

elf2e32 : Error: E1036: Symbol <symbol_name > Missing from ELF file: <file_name >

The symbol (function) is present in the generated ELF DLL, but it is not visible externally. This is because the symbol (function) definition is not annotated with EXPORT_C, or when callers within the DLL does not prefix the function declaration with the IMPORT_C modifier.

Identify such symbol definitions and annotate them with the EXPORT_C modifier. Prefix the function declaration with the IMPORT_C modifier if you are trying to call a function in another DLL.

If you are unable to troubleshoot the problems listed in this table, perform the following steps:

  1. Browse to the directory where the object files of your component are stored.

  2. Create a dump of the symbol table for each object file using the command, fromelf -s <object_filename> and locate the problematic function. If the function does not have the STV_DEFAULT visibility, then you have found the cause, or at least have identified the source file that is causing the problem.

  3. If you are still unable to identify the cause of the problem, check the pre-processed source file to find out the cause. Perform the following steps to pre-process the source file:

    1. Identify the armcc command (copy from the log file) that compiled the object.

    2. Run the command after replacing -c with -E and specifying the output file as an argument to the -o option.

    3. Check whether the function has been annotated with __declspec(dllimport), which is the expansion of IMPORT_C.

      Note: If the function declaration is incorrect in more than one place, then repeat this whole procedure until all instances are identified.

Overview of the - native build targets \ No newline at end of file