-
Notifications
You must be signed in to change notification settings - Fork 624
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
Retreiving neede toolchain components' tarballs fails #237
Comments
Output is in German but it tells me that there is a problem with retrieving tarball for crosstool-NG. I tried to clone the crosstool-NG project which works fine. |
I have a similar issue. cat crosstool-NG/build.log
[ALL ] Retrying.
[ALL ]
[ALL ] --2017-01-15 17:30:24-- (try: 3) http://isl.gforge.inria.fr/isl-0.14
[ALL ] Connecting to isl.gforge.inria.fr (isl.gforge.inria.fr)|128.93.193.15|:80... connected.
[ALL ] HTTP request sent, awaiting response... Read error (Connection timed out) in headers.
[ALL ] Giving up.
[ALL ]
[DEBUG] Not at this location: "http://isl.gforge.inria.fr/isl-0.14"
[ERROR]
[ERROR] >>
[ERROR] >> Build failed in step 'Retrieving needed toolchain components' tarballs'
[ERROR] >> called in step '(top-level)' |
I'm getting the same thing, just re-created a fresh build environment, with same sources as yesterday, and now it's hanging on downloading the tarballs |
it looks like the server that wasn't responding, is now responding. the tarballs get downloaded to /esp-open-sdk/crosstool-NG/.build/tarballs/ I was just now able to delete those, run "make clean" and then "make", all the tarballs were successfully downloaded this time, and compile. So alternatively you could download and place them manually from http://isl.gforge.inria.fr/
also noticed there are newer versions available, and potentially alternatively retrievable from git repo http://repo.or.cz/w/isl.git |
I can confirm that the problem is now solved. |
Check the build.log file |
goto crosstool-NG/.build/tarballs directory and download expat-2.1.0 by running:
|
Hi, I am trying to execute ct-ng build, unfortunately I encountered the same issue, I couldn't the find the directory /esp-open-sdk/crosstool-NG/.build/tarballs/. Is that something you get after the execution of build? |
For anyone living in 2021 and needing it for esp-open-sdk: Idk if this is a virus but it worked for me |
It should be |
still error |
yep, im going to do a PR with an answere above that worked |
Any ideas on how can we poke people about http://isl.gforge.inria.fr/ being down? |
You can use wayback machine to fetch the isl library until the site comes back up (https://web.archive.org/web/20210701145459/http://isl.gforge.inria.fr/isl-0.14.tar.gz) and add it to your |
I have added (https://web.archive.org/web/20210701145459/http://isl.gforge.inria.fr/isl-0.14.tar.gz) to .build but still fails |
According to your screenshot, it seems your build is looking for |
Here is giving the following error. Any ideia?
|
Had errors with both cd crosstool-NG/.build/tarballs
wget https://libisl.sourceforge.io/isl-0.14.tar.gz
wget https://github.com/libexpat/libexpat/releases/download/R_2_1_0/expat-2.1.0.tar.gz
cd -
make Seems to be compiling successfully now. |
Also had to do mkdir /tmp/tmpbin && ln -s /usr/bin/python2.7 /tmp/tmpbin/python && export PATH=/tmp/tmpbin:${PATH} from #339 to make it work, since my system already symlinks |
https://libisl.sourceforge.io/ seems to be indeed the new, official ISL site. In case it ever goes down too or moves again, gcc is mirroring the old ISL versions it depends on: A local mirror is how every project should isolate itself from external downtimes. |
I also ran into the isl & expat download issues, and then a couple of other issues that needed patches. The end result (which gets me a clean build on Ubuntu 21.10 of an apparently working toolchain) can be found here: #391 |
Anyone address this to the above kludges are not needed? |
Now (03/2023) you need to use these links:
|
Hi,
trying to build micropython myself and running repeatly into this error
KR
Christoph
The text was updated successfully, but these errors were encountered: