Linker errors when I add uart_set_divisors

john1953 wrote on Monday, August 12, 2013:

When I add uart_set_divisors I get unresolved linker errors like:
arm-none-eabi-gcc -nostdlib -L"C:\cortex\all_cortex\Debug" -L"C:\cortex\CMSISv2p00_LPC177x_8x\Debug" -Xlinker -Map=“mcub_cortex.map” -Xlinker -gc-sections -mcpu=cortex-m3 -mthumb -T “mcub_cortex_Debug.ld” -o “mcub_cortex.axf”  ./src/cr_startup_lpc17.o ./src/dip_switches_mcub.o ./src/fault_led.o ./src/lcd_idle.o ./src/lcd_main.o ./src/main.o ./src/node_stats_mcub.o ./src/tasks_mcub.o ./src/ui.o ./src/ui_menu.o ./src/ui_menu_board_list.o ./src/ui_menu_board_status.o ./src/ui_menu_generic.o ./src/ui_scr_adjust_params.o ./src/ui_scr_debug_data.o ./src/ui_scr_node_stats.o ./src/ui_scr_status_board_dips.o ./src/ui_scr_status_board_io.o   -lall_cortex -lCMSISv2p00_LPC177x_8x
c:/code_red/redsuite_5.0.12_1119/redsuite/tools/bin/…/lib/gcc/arm-none-eabi/4.6.2/…/…/…/…/arm-none-eabi/lib/armv7-m\libc.a(lib_a-abort.o): In function `abort’:
abort.c:(.text.abort+0xa): undefined reference to `_exit’
c:/code_red/redsuite_5.0.12_1119/redsuite/tools/bin/…/lib/gcc/arm-none-eabi/4.6.2/…/…/…/…/arm-none-eabi/lib/armv7-m\libc.a(lib_a-signalr.o): In function `_kill_r’:
signalr.c:(.text._kill_r+0xe): undefined reference to `_kill’
c:/code_red/redsuite_5.0.12_1119/redsuite/tools/bin/…/lib/gcc/arm-none-eabi/4.6.2/…/…/…/…/arm-none-eabi/lib/armv7-m\libc.a(lib_a-signalr.o): In function `_getpid_r’:
signalr.c:(.text._getpid_r+0x0): undefined reference to `_getpid’

This seems to be due to the 64-bit division in that routine as when I comment out the division it seems to link fine. I am using Red Suite 5 on a LPC1778 with latest FreeRTOS.

Any thoughts on what is happening?

rtel wrote on Tuesday, August 13, 2013:

Presumably your library settings are incorrect or you have to provide stubs for the library you are using. Either way I’m sure the problem is in no way FreeRTOS related so this is not the best place to ask it.

Regards.

john1953 wrote on Tuesday, August 13, 2013:

Thanks, this turned out to be a bug in Red Suite 5