• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 283 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Failure in compiling OMAPL138_StaterWare using GCC

Duy-Ky Nguyen88210
Expert 2250 points
Other Parts Discussed in Thread: OMAPL138

Hello,

I'm very excited to find OMAPL138_StarterWare, it's exactly what I've been after for quite sometime.

So, I downloaded CodeSourcery Lite 2009q1 as it includes GCC4.33 used in this package.

I'm using the latest Cygwin, probably released 2006 ?.

I failed to compile the example UART.

So I clean required libraries and try to re-compile to see if I'm ab;le to. Those libraries are : drivers, platform, system_config, ipclite, utils, usblib, grlib, nandlib.

It appears I'm able to re-compile all of them successfully.

The error relates to system LIBC and LIBGCC.

Your help is greatly appreciated.

 

Thanks,

Duy-Ky

 

Below is capture of make process

$ make clean; make all
========================= Debug LPATH -L/cygdrive/c/SW_DEV/CodeSourcery/CSL_2009q1/arm-none-eabi/lib/ -L/cygdrive/c/SW_DEV/CodeSourcery/CSL_2009q1/lib/gcc/arm-none-eabi/4.3.3/ -L../../../../../..//bin
ary/armv5/gcc/omapl138/drivers/ -L../../../../../..//binary/armv5/gcc/omapl138/evmOMAPL138/platform/ -L../../../../../..//binary/armv5/gcc/omapl138/system_config/ -L../../../../../..//binary/armv5/gcc
/omapl138/ipclite/ -L../../../../../..//binary/armv5/gcc/utils/ -L../../../../../..//binary/armv5/gcc/omapl138/usblib/ -L../../../../../..//binary/armv5/gcc/grlib/ -L../../../../../..//binary/armv5/gc
c/nandlib/ =========================
make TARGET_MODE=debug lib
make[1]: Entering directory `/home/Duy-Ky/OMAPL138_StarterWare_1_10_01_01/build/armv5/gcc/omapl138/evmOMAPL138/uart'
make[2]: Entering directory `/home/Duy-Ky/OMAPL138_StarterWare_1_10_01_01/build/armv5/gcc/omapl138/drivers'
make[2]: `debug' is up to date.
make[2]: Leaving directory `/home/Duy-Ky/OMAPL138_StarterWare_1_10_01_01/build/armv5/gcc/omapl138/drivers'
make[2]: Entering directory `/home/Duy-Ky/OMAPL138_StarterWare_1_10_01_01/build/armv5/gcc/omapl138/evmOMAPL138/platform'
make[2]: `debug' is up to date.
make[2]: Leaving directory `/home/Duy-Ky/OMAPL138_StarterWare_1_10_01_01/build/armv5/gcc/omapl138/evmOMAPL138/platform'
make[2]: Entering directory `/home/Duy-Ky/OMAPL138_StarterWare_1_10_01_01/build/armv5/gcc/omapl138/system_config'
make[2]: `debug' is up to date.
make[2]: Leaving directory `/home/Duy-Ky/OMAPL138_StarterWare_1_10_01_01/build/armv5/gcc/omapl138/system_config'
make[2]: Entering directory `/home/Duy-Ky/OMAPL138_StarterWare_1_10_01_01/build/armv5/gcc/utils'
make[2]: `debug' is up to date.
make[2]: Leaving directory `/home/Duy-Ky/OMAPL138_StarterWare_1_10_01_01/build/armv5/gcc/utils'
========================= LIB =========================
make[1]: Leaving directory `/home/Duy-Ky/OMAPL138_StarterWare_1_10_01_01/build/armv5/gcc/omapl138/evmOMAPL138/uart'
make TARGET_MODE=Debug bin
make[1]: Entering directory `/home/Duy-Ky/OMAPL138_StarterWare_1_10_01_01/build/armv5/gcc/omapl138/evmOMAPL138/uart'

========================= BIN LPATH -L/cygdrive/c/SW_DEV/CodeSourcery/CSL_2009q1/arm-none-eabi/lib/ -L/cygdrive/c/SW_DEV/CodeSourcery/CSL_2009q1/lib/gcc/arm-none-eabi/4.3.3/ -L../../../../../..//binar
y/armv5/gcc/omapl138/drivers/Debug -L../../../../../..//binary/armv5/gcc/omapl138/evmOMAPL138/platform/Debug -L../../../../../..//binary/armv5/gcc/omapl138/system_config/Debug -L../../../../../..//bin
ary/armv5/gcc/omapl138/ipclite/Debug -L../../../../../..//binary/armv5/gcc/utils/Debug -L../../../../../..//binary/armv5/gcc/omapl138/usblib/Debug -L../../../../../..//binary/armv5/gcc/grlib/Debug -L.
./../../../../..//binary/armv5/gcc/nandlib/Debug =========================

arm-none-eabi-gcc  -c -g -fdata-sections -ffunction-sections -Wall -I../../../../../..//include -I../../../../../..//include/hw -I../../../../../..//include/armv5 -I../../../../../..//include/armv5/om
apl138 -I../../../../../..//grlib/include -I../../../../../..//usblib/include -I../../../../../..//ipclite/include -I../../../../../..//nandlib/include -I"/cygdrive/c/SW_DEV/CodeSourcery/CSL_2009q1/in
clude" -Domapl138 -DevmOMAPL138 ../../../../../../examples/evmOMAPL138/uart//*.c
arm-none-eabi-ld -e Entry -u Entry -u __aeabi_uidiv -u __aeabi_idiv --gc-sections -L"/cygdrive/c/SW_DEV/CodeSourcery/CSL_2009q1/arm-none-eabi/lib/" -L"/cygdrive/c/SW_DEV/CodeSourcery/CSL_2009q1/lib/gc
c/arm-none-eabi/4.3.3/" -L../../../../../..//binary/armv5/gcc/omapl138/drivers/Debug -L../../../../../..//binary/armv5/gcc/omapl138/evmOMAPL138/platform/Debug -L../../../../../..//binary/armv5/gcc/oma
pl138/system_config/Debug -L../../../../../..//binary/armv5/gcc/omapl138/ipclite/Debug -L../../../../../..//binary/armv5/gcc/utils/Debug -L../../../../../..//binary/armv5/gcc/omapl138/usblib/Debug -L.
./../../../../..//binary/armv5/gcc/grlib/Debug -L../../../../../..//binary/armv5/gcc/nandlib/Debug -o Debug/uartEcho.out -Map Debug/uartEcho.map \
              Debug/*.o* -T uartEcho.lds -ldrivers -lutils -lplatform -lsystem_config -lc -lgcc
C:\SW_DEV\CodeSourcery\CSL_2009q1\bin\arm-none-eabi-ld.exe: cannot find -lc
make[1]: *** [bin] Error 1
make[1]: Leaving directory `/home/Duy-Ky/OMAPL138_StarterWare_1_10_01_01/build/armv5/gcc/omapl138/evmOMAPL138/uart'
make: *** [debug] Error 2

$

 

 

 

  • 0
    TI__Expert 8890 points

    Duy-Ky,

    This error is caused by the linker not being able to find the standard, toolchain-provided libraries (i.e. libc.a).  Before building the StarterWare GCC makefiles, you should export your GCC toolchain to the LIB_PATH environment variable.  In Cygwin on my PC, I use the following command:

    $ export LIB_PATH="C:\Program Files\CodeSourcery\Sourcery G++ Lite"

    This may look different on your PC depending on where the toolchain is installed (or if you're using a different shell, etc.).  Please try setting this environment variable, then clean and rebuild the application.