i can't install isl 0.14

[curla92]

i tried to put manual the file into tarballs folder but when i try to compile i have an error.
This error says that missing the configure file of ISL 0.14.

How can i solve this ? thank y

[renandw]

I am struggling with this too

[glenn20]

Not directly answering the question, but, I used the following patch to correct the download url for isl 0.14:

--- a/scripts/build/companion_libs/121-isl.sh
+++ b/scripts/build/companion_libs/121-isl.sh
@@ -14,7 +14,8 @@ if [ "${CT_ISL}" = "y" ]; then
 # Download ISL
 do_isl_get() {
     CT_GetFile "isl-${CT_ISL_VERSION}" \
-        http://isl.gforge.inria.fr
+        ftp://gcc.gnu.org/pub/gcc/infrastructure
+        # http://isl.gforge.inria.fr
 }
 
 # Extract ISL

I hope that's helpful. Worked for me, but I'm not sure what the canonical source should be or why the manual method failed.

For those not familiar with patches (so old school), save the snippet as eg. ~/crosstool-NG-isl.patch, then:

cd esp-open-sdk/crosstool-NG
patch -p1 < ~/crosstool-NG-isl.patch

[renandw]

I've looked into that:
#237

it solves for me

[renandw]

thanks for the response @glenn20

[eku]

@glenn20 the ftp-protocol will fail in environments where only http(s) is allowed (company firewall). The files at gnu.org can be downloaded via http(s) too.

[ChrisMacGregor]

I had to make a similar change in 210-expat.sh in crosstool-NG/scripts/build/companion_libs/210-expat.sh , replacing:

  `http://downloads.sourceforge.net/project/expat/expat/${CT_EXPAT_VERSION}`

with:

  `https://src.fedoraproject.org/repo/pkgs/expat/expat-${CT_EXPAT_VERSION}.tar.gz/dd7dab7a5fea97d2a6a43f511449b7cd`

because expat-2.1.0.tar.gz on sourceforge had been renamed to "expat-2.1.0-RENAMED-VULNERABLE-PLEASE-USE-2.3.0-INSTEAD.tar.gz"... I considered seeing if it would work using 2.3.0 as suggested, but 2.3.0 similarly redirects to 2.4.1, and for the moment I'm not concerned about it. This should probably be fixed, but it looks like no one has touched these tools for years now.

Note that the above changes had no effect when I simply restarted the build by running make again; I had to also make the same changes here:
crosstool-NG/lib/crosstool-ng-1.22.0-60-g37b07f6f/scripts/build/companion_libs/121-isl.sh
crosstool-NG/lib/crosstool-ng-1.22.0-60-g37b07f6f/scripts/build/companion_libs/210-expat.sh)

However, that was not necessary when I patched those files before starting the build.

Note also that I subsequently ran into 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
https://github.com/ChrisMacGregor/esp-open-sdk/tree/builds-on-Ubuntu-21.10
Tarball of built toolchain: https://github.com/ChrisMacGregor/esp-open-sdk/releases/tag/builds-on-Ubuntu-21.10

[PsuFan]

I cant get isl 0.14 or expat-2.1.0. Patches didn't work for me. Everyone's "updated" "maintained" forks didn't work for me either. They don't even bother to update the readme. Download manually from http://mirror.opencompute.org/onie/crosstool-NG/ and place in esp-open-sdk/crosstool-NG/.build/tarballs

I WISH SOMEONE WOULD MAINTAIN ACTUAL INSTRUCTIONS ON HOW TO INSTALL MICROPYTHON FOR ESP8266 INCLUDING ALL COMMANDS, INCLUDING GIT, MODIFICATIONS TO $PATH ETC. I was screwed for a while with $PATH because I used ~ which worked fine for me but not compiler...

[igagis]

@PsuFan see micropython/micropython#8163 , it is an open issue

[ChrisMacGregor]

I cant get isl 0.14 or expat-2.1.0. Patches didn't work for me. Everyone's "updated" "maintained" forks didn't work for me either. They don't even bother to update the readme. Download manually from http://mirror.opencompute.org/onie/crosstool-NG/ and place in esp-open-sdk/crosstool-NG/.build/tarballs

I WISH SOMEONE WOULD MAINTAIN ACTUAL INSTRUCTIONS ON HOW TO INSTALL MICROPYTHON FOR ESP8266 INCLUDING ALL COMMANDS, INCLUDING GIT, MODIFICATIONS TO $PATH ETC. I was screwed for a while with $PATH because I used ~ which worked fine for me but not compiler...

@PsuFan Does https://github.com/ChrisMacGregor/esp-open-sdk work for you?

Fair point about the readme files. I didn't because I was trying to keep my repo as close as possible to the original, but there's probably no harm in updating the readme.