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
Warnings logged on build that toolchain version is not supported #226
Comments
You may want to check the output of the actual commands on your system since your output seems to show null for both items https://github.com/espressif/esp-idf/blob/master/make/project.mk#L432 |
This is on Linux, yes? I remember Ubuntu, but which version? Despite the warning, does the build run correctly? There is a bug that if the path to the toolchain needs to be set in menuconfig, it will print a warning like this before the path is configured. However it looks like the toolchain is already on your PATH, so it may be something else in this case. |
@nkolban do you only get this the first time you run 'make'? |
This isn't working right for me either - and now I see why. I'm racing out the door but here's the fix for
Why? Because if you're using Windows executables it reports with .exe:
|
Thanks @MartyMacGyver . We'll have a fix for Windows version detection out shortly. |
The make appears clean ... i.e. it runs to complete. If I then run make clean and make again, the warnings are still present. |
OK, thanks @nkolban for the update. We have a fix for both these issues (warning on a clean build, warning on Windows) which will be merged shortly. |
The fix should be one and the same. |
They're not, but they're similar. |
I have boiled it down to on linux |
Thanks for that extra detail @Frida854 . There's a fix in the pipeline for this warning, which is two different underlying issues depending on platform:
|
Am using ESP-IDF as of the date of this issue. I got a warning that my toolchain was not supported. Great that there is a check. However, after installing the latest toolchain, I continue to get the same error. Here is a text capture of what I am seeing:
As you can see, the execution of my
xtensa-esp32-elf-gcc
is producing the version that appears to be expected but yet the error is still logged.The text was updated successfully, but these errors were encountered: