-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Misconfigured environment #24733
Comments
@Nukersson is your GNU Arm Embedded toolchain installed in and then install it in a fixed directory and point to it via the |
|
@Nukersson how did you install GNU Arm Embedded? |
My GNU Arm Embedded environment installed according to toolchain-gnuarmemb P.S: I've updated west/zephyr today and the behavior is no more there. |
Thanks, will close the issue then. |
HI I have the same issue. |
CROSS_COMPILE: /Users/alex/toolchains/arm/bin/bin/arm-none-eabi- Why is it bin/bin? |
I think, It is fixed already. Thus it can not be, that it not works for you. I've installed completely new Ubuntu 20.04 virtual machine with latest Zephyr toolchain like it done in corresponding Docker file @ line 111 about a month ago and it worked nicely for me. P.S.: please read some of my posts above - there I explained, why bin/bin is a mistake. |
Hi, Here are my env vars: Is there some way to reset any cached things in the build system? I did have a different env var at the start. Here is the full output, showing the vesrion of Zephry (dsp-quantized-too-big-fix) benchmark-fw $ ZEPHYR_BASE=~/work/tool-repos/zephyr/zephyr/ west build -p auto -b stm32f4_disco . The cmake-policies(7) manual explains that the OLD behaviors of all -- Application: /Users/alex/work/edgeimpulse/studio/dsp-pipeline/server/benchmark-fw User-configuration: ZEPHYR_TOOLCHAIN_VARIANT: gnuarmemb Internal variables: CROSS_COMPILE: /Users/alex/toolchains/arm/bin/bin/arm-none-eabi- TOOLCHAIN_HOME: /Users/alex/toolchains/arm/bin Call Stack (most recent call first): |
Ok, I figured it out. If you need to change your toolchain path (GNUARMEMB_TOOLCHAIN_PATH) you need to delete your build folder first. Otherwise, west uses some cached copy of that path |
It is always a very good idea to remove your build folder after each toolchain / west update and / or git pull. |
It's not just a good idea, it is necessary, I hit this issue after a clean Docker image install/update then project compile, it was only eventually resolved by removing the |
Ran into issue:
Fixed by setting |
Building on of the existing examples leads to misconfigured environment error.
Steps to reproduce on mac OS X 10.15.4:
Checkout master using tutorial Getting Started Guide
( in my case: West version: v0.7.2 and master of Zephyr's project )
Run build of an existing example project:
west build -b nucleo_l432kc samples/hello_world
Get the error:
Obviously the error is in environment variable:
Following temporar fix works for me:
In the file:
add following command:
The text was updated successfully, but these errors were encountered: