Skip to content
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

Closed
nkolban opened this issue Jan 13, 2017 · 11 comments
Closed

Warnings logged on build that toolchain version is not supported #226

nkolban opened this issue Jan 13, 2017 · 11 comments
Milestone

Comments

@nkolban
Copy link
Contributor

nkolban commented Jan 13, 2017

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:

$ xtensa-esp32-elf-gcc --version
xtensa-esp32-elf-gcc (crosstool-NG crosstool-ng-1.22.0-61-gab8375a) 5.2.0
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ make
WARNING: Toolchain version is not supported: 
Expected to see version: crosstool-NG crosstool-ng-1.22.0-61-gab8375a
Please check ESP-IDF setup instructions and update the toolchain, or proceed at your own risk.
/home/kolban/esp32/esptest/esp-idf/make/project.mk:445: WARNING: Compiler version is not supported: 
Expected to see version(s): 5.2.0
Please check ESP-IDF setup instructions and update the toolchain, or proceed at your own risk.

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.

@negativekelvin
Copy link
Contributor

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

@projectgus
Copy link
Contributor

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.

@projectgus
Copy link
Contributor

@nkolban do you only get this the first time you run 'make'?

@MartyMacGyver
Copy link

MartyMacGyver commented Jan 13, 2017

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 project.mk:

TOOLCHAIN_COMMIT_DESC := $(shell $(CC) --version | sed -E -n 's|xtensa-esp32-elf-gcc.*\ \(([^)]*).*|\1|gp')
TOOLCHAIN_GCC_VER := $(shell $(CC) --version | sed -E -n 's|xtensa-esp32-elf-gcc.*\ \(.*\)\ (.*)|\1|gp')

Why? Because if you're using Windows executables it reports with .exe:

$ xtensa-esp32-elf-gcc --version
xtensa-esp32-elf-gcc.exe (crosstool-NG crosstool-ng-1.22.0-61-gab8375a) 5.2.0
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

@projectgus
Copy link
Contributor

Thanks @MartyMacGyver . We'll have a fix for Windows version detection out shortly.

@nkolban
Copy link
Contributor Author

nkolban commented Jan 13, 2017

@projectgus

The make appears clean ... i.e. it runs to complete.

If I then run make clean and make again, the warnings are still present.

@projectgus
Copy link
Contributor

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.

@MartyMacGyver
Copy link

The fix should be one and the same.

@projectgus
Copy link
Contributor

They're not, but they're similar.

@igrr igrr added the Status: In Progress Work is in progress label Jan 15, 2017
@Frida854
Copy link

I have boiled it down to on linux
export CONFIG_TOOLPREFIX=$(pwd)/xtensa-esp32-elf/bin/xtensa-esp32-elf-
before I ran
make duktape_configure and
make
then it sorted it out for me.

@projectgus
Copy link
Contributor

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:

  • Windows doesn't detect toolchain correctly
  • If the toolchain needs to be set in menuconfig before it works (ie not in PATH, or has a different prefix to the default prefix), then the warning appears on a clean build (until after "menuconfig" or "defconfig") has run.)

@igrr igrr closed this as completed in 5c9c08e Jan 16, 2017
@igrr igrr removed Status: In Progress Work is in progress labels Jan 16, 2017
@igrr igrr modified the milestone: v2.0 Jan 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants