Compile fails for long arg list in build_profile
See original GitHub issueAlmost exactly the same issue as https://github.com/ARMmbed/mbed-cli/issues/339
- mbed-cli: 1.8.1
- arm-none-eabi-g++ (GNU Tools for Arm Embedded Processors 7-2018-q2-update) 7.3.1 20180622 (release) [ARM/embedded-7-branch revision 261907]
- macOS High Sierra 10.13.6
micbar02 @ C02SP20YFVH4 ~/git/tf/rom-demo/utensor-mnist-demo (f/rom-tensor *)
└─ $ ▶ mbed compile -vv --profile=utensor/build_profile/release.json
...
[mbed-24823] Exec "/Users/micbar02/anaconda2/bin/python -u /Users/micbar02/git/tf/rom-demo/utensor-mnist-demo/mbed-os/tools/make.py -t gcc_arm -m DISCO_F413ZH --profile utensor/build_profile/release.json --source . --build ./BUILD/DISCO_F413ZH/GCC_ARM-RELEASE -v" in "/Users/micbar02/git/tf/rom-demo/utensor-mnist-demo"
Building project utensor-mnist-demo (DISCO_F413ZH, GCC_ARM)
Scan: .
Scan: mbed
Scan: env
[DEBUG] Macros: -D__MBED__=1 -DDEVICE_I2CSLAVE=1 -D__FPU_PRESENT=1 -DDEVICE_PORTOUT=1 -DUSBHOST_OTHER -DDEVICE_PORTINOUT=1 -DTARGET_RTOS_M4_M7 -D__CMSIS_RTOS -DDEVICE_LOWPOWERTIMER=1 -DDEVICE_RTC=1 -DTOOLCHAIN_object -DDEVICE_SERIAL_ASYNCH=1 -DTARGET_STM32F4 -DTARGET_DISCO_F413ZH -DTOOLCHAIN_GCC -DDEVICE_CAN=1 -DTARGET_CORTEX_M -DDEVICE_I2C_ASYNCH=1 -DTARGET_LIKE_CORTEX_M4 -DDEVICE_ANALOGOUT=1 -DTARGET_M4 -DTARGET_UVISOR_UNSUPPORTED -DDEVICE_ANALOGIN=1 -DDEVICE_SPI_ASYNCH=1 -DDEVICE_PWMOUT=1 -DDEVICE_INTERRUPTIN=1 -DTARGET_CORTEX -DDEVICE_I2C=1 -DTRANSACTION_QUEUE_SIZE_SPI=2 -D__CORTEX_M4 -DDEVICE_STDIO_MESSAGES=1 -DTARGET_FAMILY_STM32 -DTARGET_FF_ARDUINO -DDEVICE_PORTIN=1 -DTARGET_RELEASE -DTARGET_STM -DDEVICE_SERIAL_FC=1 -DTARGET_STM32F413xH -DDEVICE_TRNG=1 -DTARGET_LIKE_MBED -D__MBED_CMSIS_RTOS_CM -DDEVICE_SLEEP=1 -DTOOLCHAIN_GCC_ARM -DTARGET_STM32F413xx -DDEVICE_SPI=1 -DUSB_STM_HAL -DTARGET_STM32F413ZH -DDEVICE_SPISLAVE=1 -DMBED_BUILD_TIMESTAMP=1537200319.87 -DDEVICE_SERIAL=1 -DDEVICE_FLASH=1 -DARM_MATH_CM4
Compile [ 0.2%]: ft6x06.c
[DEBUG] Compile: arm-none-eabi-gcc -std=gnu99 -c -Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -fmessage-length=0 -fno-exceptions -fno-builtin -ffunction-sections -fdata-sections -funsigned-char -MMD -fno-delete-null-pointer-checks -fomit-frame-pointer -Os -DNDEBUG -mcpu=cortex-m4 -mthumb -mfpu=fpv4-sp-d16 -mfloat-abi=softfp -D__MBED__=1 -DDEVICE_I2CSLAVE=1 -D__FPU_PRESENT=1 -DDEVICE_PORTOUT=1 -DUSBHOST_OTHER -DDEVICE_PORTINOUT=1 -DTARGET_RTOS_M4_M7 -D__CMSIS_RTOS -DDEVICE_LOWPOWERTIMER=1 -DDEVICE_RTC=1 -DTOOLCHAIN_object -DDEVICE_SERIAL_ASYNCH=1 -DTARGET_STM32F4 -DTARGET_DISCO_F413ZH -DTOOLCHAIN_GCC -DDEVICE_CAN=1 -DTARGET_CORTEX_M -DDEVICE_I2C_ASYNCH=1 -DTARGET_LIKE_CORTEX_M4 -DDEVICE_ANALOGOUT=1 -DTARGET_M4 -DTARGET_UVISOR_UNSUPPORTED -DDEVICE_ANALOGIN=1 -DDEVICE_SPI_ASYNCH=1 -DDEVICE_PWMOUT=1 -DDEVICE_INTERRUPTIN=1 -DTARGET_CORTEX -DDEVICE_I2C=1 -DTRANSACTION_QUEUE_SIZE_SPI=2 -D__CORTEX_M4 -DDEVICE_STDIO_MESSAGES=1 -DTARGET_FAMILY_STM32 -DTARGET_FF_ARDUINO -DDEVICE_PORTIN=1 -DTARGET_RELEASE -DTARGET_STM -DDEVICE_SERIAL_FC=1 -DTARGET_STM32F413xH -DDEVICE_TRNG=1 -DTARGET_LIKE_MBED -D__MBED_CMSIS_RTOS_CM -DDEVICE_SLEEP=1 -DTOOLCHAIN_GCC_ARM -DTARGET_STM32F413xx -DDEVICE_SPI=1 -DUSB_STM_HAL -DTARGET_STM32F413ZH -DDEVICE_SPISLAVE=1 -DMBED_BUILD_TIMESTAMP=1537200319.87 -DDEVICE_SERIAL=1 -DDEVICE_FLASH=1 -DARM_MATH_CM4 @./BUILD/DISCO_F413ZH/GCC_ARM-RELEASE/.includes_7d2d57ac3ad0714f93c9bb5b82d4592c.txt -include ./BUILD/DISCO_F413ZH/GCC_ARM-RELEASE/mbed_config.h -MD -MF BUILD/DISCO_F413ZH/GCC_ARM-RELEASE/BSP_DISCO_F413ZH/Drivers/BSP/Components/ft6x06/ft6x06.d -o BUILD/DISCO_F413ZH/GCC_ARM-RELEASE/BSP_DISCO_F413ZH/Drivers/BSP/Components/ft6x06/ft6x06.o ./BSP_DISCO_F413ZH/Drivers/BSP/Components/ft6x06/ft6x06.c
[DEBUG] Return: 1
[DEBUG] Output: arm-none-eabi-gcc: error trying to exec '/Users/micbar02/gcc/gcc-arm-none-eabi-7-2018-q2-update/bin/../lib/gcc/arm-none-eabi/7.3.1/cc1': execv: Argument list too long
Traceback (most recent call last):
File "/Users/micbar02/git/tf/rom-demo/utensor-mnist-demo/mbed-os/tools/make.py", line 296, in <module>
stats_depth=options.stats_depth)
File "/Users/micbar02/git/tf/rom-demo/utensor-mnist-demo/mbed-os/tools/build_api.py", line 533, in build_project
objects = toolchain.compile_sources(resources, resources.inc_dirs)
File "/Users/micbar02/git/tf/rom-demo/utensor-mnist-demo/mbed-os/tools/toolchains/__init__.py", line 928, in compile_sources
return self.compile_queue(queue, objects)
File "/Users/micbar02/git/tf/rom-demo/utensor-mnist-demo/mbed-os/tools/toolchains/__init__.py", line 991, in compile_queue
raise ToolException(err)
ToolException: arm-none-eabi-gcc: error trying to exec '/Users/micbar02/gcc/gcc-arm-none-eabi-7-2018-q2-update/bin/../lib/gcc/arm-none-eabi/7.3.1/cc1': execv: Argument list too long
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
"Arguments too long" error when including a large number of ...
When placing a folder with a large number of tiles, inside the project sources directory, the Makefile will iterate through all the sub- ......
Read more >Compiling C++ code with Bazel fails due to "Argument list too ...
I have a huge project which consists of many libraries that are tied together (deps). When compiling, Bazel creates the famous virtual includes ......
Read more >Swift 5.5+ error, argument list is too long
When we build it on Xcode 12.5.1, everything is ok. When we tried to build it on Xcode 13+, getting compile error "Argument...
Read more >Introduction to build profiles - Apache Maven
Profiles can be explicitly specified using the -P command line flag. This flag is followed by a comma-delimited list of profile IDs to...
Read more >Optimize your build speed | Android Developers
Long build times slow down your development process. This page provides some techniques to help resolve build speed bottlenecks.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@cmonr DAMMIT, I’ve had issues similar to this in the past. It’s caused by having a Python virtualenv in my project repo. Closing the ticket
@mbartling Even though this isn’t what we thought, it’s still a significant-enough issue worth tracking.
Would you mind opening another issue for others to reproduce and so that we can fix?