jam7 / chromebrew Goto Github PK

Current implementation uses pre-compiled toolchains and they require symbolic links from ~/Downloads.

It's better to use different toolchains.

Recently, I'd had an issue installing packages back to back resulting in a checksum mismatch, perhaps due to throttling from github.com

When the error occurs, crew no longer works. It turns out device.json gets blanked somehow and then the crew script can't continue. Perhaps the logic should be rewritten to ensure this doesn't happen.

Hi,
I'm trying to build gcc 7.2 from sources (after I've installed buildessential) but I always seem to have some linker error:

/usr/local/bin/ld: cannot find crt1.o: No such file or directory
/usr/local/bin/ld: cannot find crti.o: No such file or directory

although both files are in /usr/local/lib64.

A similar one I get when the linker tries to find libmvec_nonshared this the linker seems to search it in /usr/lib64, libmvec_nonshared is also in /usr/local/lib64

Do I need to define any environment variable prior to trying to build GCC ?

Thanks

Just wondering if there is a reason not to use the newer versions included in packages?

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 ?

Informed by #2. This is a bug need to be solved.