-
Notifications
You must be signed in to change notification settings - Fork 1
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
make download error #2
Comments
Thank you using it. I may forget to upload it. I'll upload it in few hours. If you don't wait, it is also possible to build it by yourself with "crew binstall make". |
Thank you for response. Tried that already it still tried to download binary and failed there. |
I've uploaded make-4.2 binaries for all architecture. Thank you for filing this issue. 👍 |
noticed. Thank you. 2017-02-17 11:20:21 (190 KB/s) - 'pkgconfig-0.29.1-chromeos-x86_64.tar.xz' saved [551488/551488] Checksum mismatch :/ try again |
I've uploaded pkgconfig. I am also now uploading all binaries I might forget to upload. |
I've uploaded all binaries I need to upload. So, I think you don't have any download erros for now... Let me know if you have any problems. Thank you. |
Seems to work well. Seems like symbolic issue |
Interesting. I don't have that error on my x86_64 machine. link.sh: $LINK_AS_NEEDED set to 'yes': invoking linker directly. I guess your machine has better CPU with SIMD unit since it says
|
here is my "uname -a" result 👍 |
Hmm. Hard to solve this issue for now. Don't you mind to use pre-compiled version of vim? I think I can upload my binary and it will work on your environment too. |
Sure. No problem. I am just trying to add my value here. |
strange, since original repository was working before i erased my entire computer and start with this one (which seems to have newer versions) |
@shayf Please performs This livmvec_nonshared.a stuff is new to me. I'll check details. I wish I could reproduce the problem here. |
Done and working. |
Thanks. I'll do. |
@shayf Is it possible to perform:
On my machine I see only:
Your machine may have libmvec_nonshared.a somewhere. Thanks. |
sure.
|
@shayf Thanks. It says Can you show me your /lib64? I'm thinking your chromeos using newer glibc. Please show me the result of |
Sure.
|
Nice. Now we understand the source of problem. Your OS uses glibc 2.23 although my chromebrew uses glibc 2.19 and the original one uses 2.17. Thank you for the help. This problem will happens if you try to compile files with I think it is possible to solve this problem by providing libmvec_nonshared.a as an additional package. Give me a few days for that. ;) |
much appreciated. Could it be due the fact i am using Canary channel ? |
Ahh yes, very yes. 👍 |
so, let me try on DEV channel. I just do not remember how to get out of canary. Will Google it. |
It's not a problem. Canary will out as stable soon anyway. If you really want to get out of canary, it's fine though. |
OK. |
So, it will out in a few months anyway. |
Seems like that. |
@shayf Hi. I made glibc223.rb to install glibc-2.23 over existing glibc-2.19. Please do following step by hand. In near future, I will repace glibc.rb with this glibc223.rb, but I'm not sure whether it is safe on stable channel for now.
|
i have compiled using the stable channel (due 2.19 used there) |
If so, not really need to switch back to another channel. Actually, I already switched to beta channel and tested it by myself. Just want to inform you it is ready. :) |
Closing this issue since problems are solved. Thank you @shayf |
HI, strange issue.
Just installed o fresh Chromebook (x86_64, Lenovo 100S), and while trying to install any package, i get the following :
Found make, version 4.2
Precompiled binary available, downloading...
--2017-02-17 09:39:36-- https://github.com/jam7/chromebrew/releases/download/binaries/make-4.2-chromeos-x86_64.tar.xz
Resolving github.com... 192.30.253.113, 192.30.253.112
Connecting to github.com|192.30.253.113|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-02-17 09:39:37 ERROR 404: Not Found.
Could it be the binary was removed ?
The text was updated successfully, but these errors were encountered: