Compiler/TMS320C6678: Problems building Libc.a archive

Please understand that libc.a is not an object library, or a source code library.  It is an index library.  An index library is a collection of several object file library variants, which is useful when several variants of a library with different options are available.  It is created with the library information archiver libinfo6x.  Please read more about it in the section titled Library Information Archiver Description in the C6000 assembly language tools manual.

If that doesn't clear things up, please show one example of what you attempted.  By copy-n-paste, show the exact command, and all the resulting diagnostics.

Thanks and regards,

-George

Please tell me more about your host environment.  Windows or Linux?  Do you build from within CCS?  Or on the command line?

What version of the compiler?

Please show all the system response to that mklib command.

Thanks and regards,

-George

Okay, there are two distinct errors happening here:

1. The library failed to build (evidenced by "ERROR: mklib: gmake error during ... build")
2. The linker had an internal error

We're not going to be able to address #2 until we get a complete, reproducable test case, so let's tackle #1

You've given us just the last bit of the build log.  There must have been another error message earlier in the log.  Please attach the entire build console to this thread so that we can examine the errors.

console.logHi Archaeologist,

in attach here is the requested log.

Thanks and regards,

Vittorio

The first error, and the cause of all the others, is "'[' is not recognized as an internal or external command"

mklib uses gmake to build the libraries.  gmake invokes sh.exe.  '[' is a sh.exe built-in.  Thus, if '[' is not recognized, then this suggests that the make process is invoking the wrong version of gmake or sh.exe.

Do you use Cygwin?  Do you use MSYS?  Do you use any other Unix-interface-providing utility on that Windows machine?

Do you have a version of gmake or sh.exe installed other than the ones provided in the CCS distribution?  Does your PATH variable put these other versions before the ones in CCS?  You need %CCSROOT%\utils\bin\gmake.exe and %CCSROOT%\utils\cygwin\sh.exe to be found first.

Do any of these things apply to you?

HI Archaeologist,

as mentioned before, I've forced the mklib to use TI compiler (mklib.exe --pattern=rtd6600_elf.lib --gmake=ccsv7\utils\bin\gmake) also in CCS but it doesn't work.

Any suggest about that?

Thanks in advance,

Vittorio

Hi guys,
we started from a brand new environment putting all the steps (described in the topic) in a script automatizing the process.

Here is the batch script:

REM customize the following variable with your TI installation
set TI_INSTALL_DIR=C:\ti_ccs7_2
set CCS_INSTALL_DIR=%TI_INSTALL_DIR%\ccsv7
set TI_CGT_DIR=ti-cgt-c6000_8.1.3
set TI_CGT_LIB_DIR=%TI_INSTALL_DIR%\%TI_CGT_DIR%\lib


REM remove all other entry from PATH variable
set PATH=%CCS_INSTALL_DIR%\utils\cygwin;%CCS_INSTALL_DIR%\utils\bin;%TI_INSTALL_DIR%\xdctools_3_32_02_25_core;%TI_INSTALL_DIR%\xdctools_3_32_02_25_core\bin;%CCS_INSTALL_DIR%\tools\compiler\ti-cgt-c6000_8.1.3\bin

REM change on TI_CGT_LIB_DIR
cd %TI_CGT_LIB_DIR%

REM rebuild libraries
mklib.exe --all

The procedure was successful. In our environment the CCS compiler is not included in our PATH.

Thanks in advance,
Vittorio