-
Notifications
You must be signed in to change notification settings - Fork 63
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
Move to xenial from trusty #69
Conversation
OK I played around a bit. When I download the file ( The mount parameters of /opt/nodemcu-firmware are exactly the same on both versions. So it seems to be related to xenial, I don't see how though. |
That is different on macOS. On the host OS I can unpack it just fine. |
Somehow my setup was inconsistent. Now it works. If that's the problem at all |
This doesn't help but we're close. |
In the other issue it was also mentioned that the tar contains links. Do they work under Windows? Ok I will try this afternoon. |
@jmattsson this is a weird one, really.
I also tried with |
Those weird permissions aren't in the tarball. You can verify that for yourself with a It sounds to me that you have a |
It's probably also not a problem of docker but of running as root where tar runs without the |
Sorry, I should have mentioned that I had verified that already.
What I also verified is that |
Ah, I looked at the 8266 toolchain. Yes, I can see those odd permissions in the 32 on my end too. Let me see if now would be a good time to build & release a new toolchain... |
Okay, at least the esp32 toolchain has been updated since I built the last toolchains. I'll kick off new builds and pay extra attention to what goes into the tar file this time. |
Marcel, could you try this version instead? https://github.com/jmattsson/esp-toolchains/releases/tag/linux-x86_64-20190731.0 |
Yep, that one works (only tested ESP32 untaring). |
Maybe easiest to just switch over to that, than you digging further into the hole on OS X? |
Thank you for helping out here! I appreciate that.
Yep, looking forward to you patching https://github.com/nodemcu/nodemcu-firmware/blob/dev-esp32/Makefile#L9
Not sure I understand. Regardless of which way I run |
Stop selling yourself short, Marcel - I have full confidence in you PR'ing such a change :D As for the other comment, I was referring to @HHHartmann's first post above. |
for what it's worth, that esp32 version uncompresses without error on OS X (unlike the earlier version). |
FYI on OSX the updated updated code (commit nodemcu/nodemcu-firmware@7ad6bc1) runs configure-esp32 nicely out of the box. But the build fails quite a way in to the process (for me):
|
Yes, I know but it's unrelated to this PR. Thus, I won't be commenting on that further. @HHHartmann implemented creating LFS images for ESP8266 a while ago. At that time there was no LFS for ESP32. That was only added just recently by @jmattsson in nodemcu/nodemcu-firmware#2801. I haven't looked into why this breaks the ESP32 build script here. In the end it's just calling |
(looks like a missing |
Didn't remember we had the list of required packages neatly documented at https://nodemcu.readthedocs.io/en/dev-esp32/build/#ubuntu. |
It's a recent addition, thank Javier for it :) |
FYI The recent update fixed the readline. Now doing a build on OSX throws the following:
|
No description provided.