Quantcast
Channel: Tools
Viewing all articles
Browse latest Browse all 91752

Forum Post: RE: Getting Error called "file"

$
0
0

[quote]fatal error: file
   "C:\StellarisWare_lm3S\grlib\ccs\Debug\grlib.lib<fontcmss30b.obj>" was built
   without VFP coprocessor support while a previously seen file was; combining
   incompatible files

[/quote]

The CCS build console is showing you the full text of the error message. Unfortunately, the message in the Problems view looks to be getting cut off after the first line due to a bug, hence all you see in the Problems view is "file" and not the rest of the message.

Now, the reason for the error itself is (as the message says) that one of the files being linked in (grlib.lib) was built without VFP support while another file was built with VFP support and the linker cannot link together such incompatible files 
file  "C:\StellarisWare_lm3S\grlib\ccs\Debug\grlib.lib<fontcmss30b.obj>" was built without VFP coprocessor support while a previously seen file was; combining incompatible files

Looking at your link command, I see a few inconsistencies:

"C:/ti/ccsv5/tools/compiler/tms470_4.9.5/bin/cl470" -mv7M4 --code_state=16 --abi=eabi -me -O2 -g --gcc --define=ccs --define=TARGET_IS_BLIZZARD_RA1 --define=PART_LM3S9B96 --diag_warning=225 --gen_func_subsections=on --ual -z --stack_size=256 -m"app_LM4F120H5QR_ccs.map" --heap_size=0 -i"C:/ti/ccsv5/tools/compiler/tms470_4.9.5/lib" -i"E:/Stellaris WS New/grlib_demo" -i"C:/ti/ccsv5/tools/compiler/tms470_4.9.5/include" --reread_libs --warn_sections --rom --relocatable --rom_model -o "grlib_demo.out"  "./utils/ustdlib.obj" "./startup_ccs.obj" "./grlib_demo.obj" "./Kentec800x480x16_SSD1963_8bit.obj" -l"C:\StellarisWare_lm3S\grlib\ccs\Debug\grlib.lib" -l"C:\ti\ccsv5\tools\compiler\tms470_4.9.5\lib\rtsv7M4_T_le_v4SPD16_eabi.lib" -l"rtsv7M4_T_le_v4SPD16_eabi.lib" "../driverlib-cm4f.lib""../lm4f120h5qr.cmd"

The part is defined as LM3S9B96, but the linker command file is for a lm4f120h5qr. Similarly, the grlib is for a LM3S while the driverlib is for a LM4F. Also the compiler build command does not have  --float_support=FPv4SPD16 which is usually there for LM4F Stellarisware projects but not there for LM3S projects.

So which part are you building for? If it is LM4F120 then make sure to use the grlib-cm4f.lib and add  --float_support=FPv4SPD16 to the compiler options. If the part is a LM3S9B96 then use the driverlib-cm3.lib and no float_support option. Also let the rts library be automatically selected based on the build options. In the project's properties, General settings, if you leave the Runtime Support library to "automatic", it will automatically pick the appropriate runtime library for the build and avoid such conflicts.

The main thing to note here is that all object files and libraries should be match up in things like abi, floating point support, endianness etc for the linker to be able to link them successfully.


Viewing all articles
Browse latest Browse all 91752

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>