AnsweredAssumed Answered

Getting "No such file or directory" linker error, but both file and directory exist.

Question asked by Rael Sasiak-Rushby on Jul 28, 2014
Latest reply on Nov 16, 2014 by dave408

In the final stages of porting a demo across into KDS, but the build keeps failing at the final linker step.

Console lists the error as:

"arm-none-eabi-g++: error: ./Sources/eGUI/eGUI_stndard_library/D4D/common_files/d4d_mouse.o: No such file or directory"

Looking in the directory I can confirm that this file exists, along with the directory.

 

It's not a path length issue as the linker command includes much longer paths, nor is it strangeness with that sub directory as the linker reports no errors about the other 14 .o files in that directory.

 

A sample of the linker command:

arm-none-eabi-g++ -mcpu=cortex-m0plus -mthumb -O0 -fmessage-length=0 -fsigned-char -ffunction-sections -fdata-sections  -g3 -T "C:/Users/B50317/Desktop/Stick_Demo__FullSource/build/kds/frdm_kl26_attach_demo/Project_Settings/Linker_Files/ProcessorExpert.ld" -Xlinker --gc-sections -L"C:/Users/B50317/Desktop/Stick_Demo__FullSource/build/kds/frdm_kl26_attach_demo/Project_Settings/Linker_Files" -Wl, -Map,"frdm_kl26_attach_demo.map" -o "frdm_kl26_attach_demo.elf" (...) ./Sources/eGUI/eGUI_standard_library/D4D/low_level_drivers/touch_screen/touch_screen_hw_interface/mcf52259_adc_12b/d4dtchhw_mcf52259_adc.o  // Example of much longer path (...) ./Sources/eGUI/eGUI_standard_library/D4D/common_files/d4d_math.o ./Sources/eGUI/eGUI_standard_library/D4D/common_files/d4d_mouse.o  //can't find ./Sources/eGUI/eGUI_standard_library/D4D/common_files/d4d_object.o ./Sources/eGUI/eGUI_standard_library/D4D/common_files/d4d_scheme.o (...)  arm-none-eabi-g++: error: ./Sources/eGUI/eGUI_stndard_library/D4D/common_files/d4d_mouse.o: No such file or directory make: *** [frdm_kl26_attach_demo.elf] Error 1

(I have attached the project build log where you can see the full linker command.)

 

Screenshot of folder, showing file exists:

Folder.png

Original Attachment has been moved to: frdm_kl26_attach_demo.build.log.zip

Outcomes