Jun 26, 2013
02:19 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jun 26, 2013
02:19 PM
Im setting up the toolchain and compiling sample applications, referencing both the 20732EclipseForAppDev.pdf and 20732AppDevWT2.pdf.Using CodeSourcery Lite via TC=gcc option, causes compilation error:"arm-none-eabi-gcc.exe: error: unrecognized command line option -falign-arrays"make: ***[brcm/bleprox/obj-A_20732A0-flash-flash/spar_setup.o] Error 1Ive tried both at command line and within Eclipse IDE along with other projects.Is this a CodeSourcery Lite version issue (currently using newest version)?Thanks,Minh
Solved! Go to Solution.
- Tags:
- 20732appdevwt2.pdf
- 20732eclipseforappdev.pdf
- [brcmbleproxobj-a_20732a0-flash-flashspar_setup.o]
- applications
- arm-none-eabi-gcc.exe
- codesourcery
- command
- compilation
- compiling
- eclipse
- error
- falign-arrays
- issue
- line
- lite
- make
- minh
- newest
- option
- projects
- referencing
- sample
- setting
- tc=gcc
- toolchain
- unrecognized
- version
1 Solution
Anonymous
Not applicable
Aug 26, 2013
02:34 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Aug 26, 2013
02:34 PM
From other post:This is a valid option with CodeSourcery G++ Lite version 2011.03-42. So you have two options, use this version of CodeSourcery or edit <adk>/spar/makecm3_gcc.inc and remove the -falign-arrays option from C_SPECIFIC_FLAGS. This will not affect the way the application gets built. The next version of the SDK will have a fix for this issue.
1 Reply
Anonymous
Not applicable
Aug 26, 2013
02:34 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Aug 26, 2013
02:34 PM
From other post:This is a valid option with CodeSourcery G++ Lite version 2011.03-42. So you have two options, use this version of CodeSourcery or edit <adk>/spar/makecm3_gcc.inc and remove the -falign-arrays option from C_SPECIFIC_FLAGS. This will not affect the way the application gets built. The next version of the SDK will have a fix for this issue.