Compiler/66AK2H12: Linker error for cpp file: multiple definition of `_write'

Bruce McKinley

Part Number: 66AK2H12

Tool/software: TI C/C++ Compiler

Getting the following linker error when trying to build a c++ project to test mailboxes in BIOS.

"C:/ti/gcc-arm-none-eabi-4_9-2015q3/bin/arm-none-eabi-gcc.exe" -mtune=cortex-a15 -marm -DSOC_K2H -DDEVICE_K2H -ffunction-sections -fdata-sections -g -gdwarf-3 -gstrict-dwarf -Wall -mfloat-abi=hard -Wl,-Map,"MailboxTest.map" -nostartfiles -static -Wl,--gc-sections -L"C:/ti/bios_6_46_05_55/packages/gnu/targets/arm/libs/install-native/arm-none-eabi/lib/fpu" --specs=rdimon.specs -o"MailboxTest.out" "./main.o" -Wl,-T"configPkg/linker.cmd" -Wl,--start-group -lgcc -lm -lnosys -lstdc++ -Wl,--end-group
makefile:145: recipe for target 'MailboxTest.out' failed
C:/ti/bios_6_46_05_55/packages/gnu/targets/arm/libs/install-native/arm-none-eabi/lib/fpu\librdimon.a(rdimon-syscalls.o): In function `_write':
/home/xlibrary/trees/gnu/gnu-c04/src/linaro/gcc-arm-none-eabi-4_7-2012q4-20121208/src/newlib/libgloss/arm/syscalls.c:425: multiple definition of `_write'
C:/ti/bios_6_46_05_55/packages/gnu/targets/arm/libs/install-native/arm-none-eabi/lib/fpu\libnosys.a(write.o):/home/xlibrary/trees/gnu/gnu-c04/src/linaro/gcc-arm-none-eabi-4_7-2012q4-20121208/src/newlib/libgloss/libnosys/write.c:19: first defined here
collect2.exe: error: ld returned 1 exit status

Any ideas?

Thanks,
Bruce

over 6 years ago

0 Archaeologist over 6 years ago

TI__Guru* 84225 points

Make sure you do not have any global variables or functions named "write" in your code.

0 Bruce McKinley over 6 years ago in reply to Archaeologist

Intellectual 760 points

No, I do not have any functions or variables named "write" in the code.

0 Archaeologist over 6 years ago

TI__Guru* 84225 points

My (wild) guess here is that both librdimon.a and libnosys.a provide a definition of write. Probably one (or both) is trying to provide a cut-down version of system I/O. It's a little bit tricky to diagnose from just the error message; it may be that write itself is not the problem, but perhaps some other variable/function in that module is used by your program and not defined in both libraries. Unfortunately, that's about all the help I'm going to be able to give you, as I'm not familiar with any of what you're using.

0 ToddMullanix over 6 years ago in reply to Archaeologist

TI__Guru* 96960 points

Hi Bruce,

Have you read this write-up: processors.wiki.ti.com/.../BIOS_with_GCC_(CortexA)

Todd

0 Bruce McKinley over 6 years ago in reply to Archaeologist

Intellectual 760 points

This was in fact the problem. I removed libnosys.a library from the linker and the program builds successfully.

Which begs the question: how does one know when to include libnosys.a or when to include librdimon.a?

0 Chester Gillon over 6 years ago in reply to Bruce McKinley

Guru 92251 points

Bruce McKinley said:
Which begs the question: how does one know when to include libnosys.a or when to include librdimon.a?

librdimon.a is used when support for Semihosting is required. Semihosting is a mechanism that enables code running on an ARM target to communicate and use the Input/Output facilities on a host computer that is running a debugger, e.g. use of printf() to report output to the CCS CIO console or fopen() to access a file on the host.

libnosys.a is used when Semihosting is not required.

Note that linking a program with librdimon.a means the program won't run when the debugger is not attached or semi hosting support is disabled in the debugger, since the start up code halts with a breakpoint instruction and waits for the debugger to resume the program.

Code Composer Studio™︎

Code Composer Studio forum

Compiler/66AK2H12: Linker error for cpp file: multiple definition of `_write'