lack of binaries for aarch64-linux-gnu

[idanre1]

Basic Infos

git://github.com/esp8266/Arduino/tools/get.py does not really support aarch64-linux-gnu.

Hardware

Hardware: ESP-01
Core Version: 2.4.0-rc2

Description

git://github.com/esp8266/Arduino/tools/get.py does not really support aarch64-linux-gnu.
I am using dragonboard 410c as a host with debian.
The OS is compiled for aarch64-linux-gnu.
the script does not recognize the os type as aarch64.
Also there are no binaries for this compilation under package/package_esp8266com_index.template.json

Settings in IDE

Issue exists in installation phase, didn't reached IDE phase yet

[devyte]

@idanre1 I could be wrong, but I don't think that is a platform that is widely used here. Feel free to propose a PR.

[idanre1]

Hi Maybe its trivial, but what is a PR? Idan Idan Regev

…

On Tue, Oct 24, 2017 at 7:31 AM, Develo ***@***.***> wrote: @idanre1 <https://github.com/idanre1> I could be wrong, but I don't think that is a platform that is widely used here. Feel free to propose a PR. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3745 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AZJDnprphrvLri75zB0-K29ykeeuaNRgks5svWg2gaJpZM4QB7yr> .

[vdeconinck]

PR = Pull Request : https://help.github.com/articles/about-pull-requests/

[devyte]

You can find tutorials online for github. An outline off the top of my head:

• Fork this repo
• create a branch within the fork
• clone locally
• make changes for your request above and commit to branch
• make the PR
• once merged, delete the branch

[igrr]

Adding binaries for aarch64 may be more involved than described above, by the way. Aside from this repo, need to update the build process in igrr/esptool-ck and igrr/mkspiffs to produce these aarch64 binaries. Also we don't have an Xtensa toolchain built for aarch64, so that needs to be built as well. It is probably worth doing at some point, for example when we update to a more recent GCC version.

…

On Wed, Oct 25, 2017, 22:16 Develo ***@***.***> wrote: You can find tutorials online for github. An outline off the top of my head: - Fork this repo - create a branch within the fork - clone locally - make changes for your request above and commit to branch - make the PR - once merged, delete the branch — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3745 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEJceiCgKbGZ7xsaw1rCcJMjJWgqZbkEks5sv0LGgaJpZM4QB7yr> .

[idanre1]

Hi Ivan Thanks for the support. Before I opened the request I was thinking compiling this git on my own to aarch64 Then I also saw the dependencies of other repos and I thought I am missing something since the get.py do have code for aarch64. Maybe we can ask igrr to help with he's repos? Regards Idan Idan Regev On Thu, Oct 26, 2017 at 2:47 AM, Ivan Grokhotkov <notifications@github.com> wrote:

…

Adding binaries for aarch64 may be more involved than described above, by the way. Aside from this repo, need to update the build process in igrr/esptool-ck and igrr/mkspiffs to produce these aarch64 binaries. Also we don't have an Xtensa toolchain built for aarch64, so that needs to be built as well. It is probably worth doing at some point, for example when we update to a more recent GCC version. On Wed, Oct 25, 2017, 22:16 Develo ***@***.***> wrote: > You can find tutorials online for github. An outline off the top of my > head: > > - Fork this repo > - create a branch within the fork > - clone locally > - make changes for your request above and commit to branch > - make the PR > - once merged, delete the branch > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#3745 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ AEJceiCgKbGZ7xsaw1rCcJMjJWgqZbkEks5sv0LGgaJpZM4QB7yr> > . > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3745 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AZJDnrsRq5U7vJyjNvj2JHPJ49M_3M5hks5sv8iIgaJpZM4QB7yr> .

[lobradov]

Bump - any news on this front? I'm also interested in aarch64 - just got a bunch of Orange Pi Prime boards that I can't use...

[igrr]

FYI, I don't think any of the active contributors is working on this (or has hardware to test this). As mentioned above, making PRs to the relevant tool repositories (esptool-ck, mkspiffs) to support aarch64 builds can help a lot!

[devyte]

Previous comment is correct. No active developer works on aarch64.
I think the critical point is building the xtensa toolchain. Whoever picks that up could also help getting an updated toolchain for everyone else (i.e.: more recent gcc!).

[igrr]

I think I can do the "more recent GCC" part, but if someone can post the right configuration for a Canadian build for aarch64 with crosstool-NG (preferably in Docker), that will be a great step towards having aarch64 support. Same for arm (v6/v7), by the way.

[herrold]

I went looking for the board, as it was unfamiliar here. I find this, and leave it as an aide for future work

at Amazon

1. This DragonBoard 410C features Qualcomm Snapdragon 410 Processor and is compliant with 96Boards specification

2. 96Boards is a 32-bit and 64-bit arm open specification maintained by the linaro 96Boards group to serve the software/maker and embedded OEM communities