-
Notifications
You must be signed in to change notification settings - Fork 7k
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
[TW#26495] Toolchain Refresh - Command "python setup.py egg_info" failed with error code 1 #2474
Comments
Problem for WARNING is the TOOLCHAIN_COMMIT_DESC changed by 1 char
|
Could you please attach the output you get when you run |
I think the solution to this may be the same as given here: Can you please try that command and see if you're able to continue? We'll update the MSYS2 package ASAP. |
Thanks for the replies. In the short term I suggest that a note be added to the installation docs to prevent others having the same problem. Q: Should I close this issue or wait for the fixed toolchain to flush through? Super support, many thanks, |
MSYS2 MINGW requires some particular MSYS2-specific packages. Closes espressif/esp-idf#2480 Closes espressif/esp-idf#2474 Closes espressif/esp-idf#2486
Environment
Problem Description
I have been working fine on the toolchain for months, but noticed a build warning appear about 'crosstool' after a recent pull and decided to do a fresh install by deleting the existing c:\msys32 folder and installing from scratch, following the instructions here for installing the master branch environment on Windows. During the install process I get an error when running the command:
python -m pip install --user -r $IDF_PATH/requirements.txt
Error:
Command "python setup.py egg_info" failed with error code 1 in :/users/simon/appdata/local/temp/pip-build-8acuzf/cffi/
subsequent builds produce the build output folders but fail to produce any app.bin file, for instance, a make on hello_world:
... ...
Running
C:/msys32/mingw32/bin/python.exe -m pip install --user -r C:/msys32/home/Simon/esp/esp-idf/requirements.txt
does not resolve the issue and errors repeat as above.Any help appreciated.
cheers,
Si.
The text was updated successfully, but these errors were encountered: