hashashini pushed to master at hashashini/example-kernel-configs-le
5 years ago
hashashini pushed to master at hashashini/example-kernel-configs-le
5 years ago
hashashini created new branch master at hashashini/example-kernel-configs-le
5 years ago
hashashini created repository hashashini/example-kernel-configs-le
5 years ago
hashashini pushed to armhf-esr60 at hashashini/tor-browser-build
5 years ago
hashashini pushed to aarch64 at hashashini/tor-browser-build
5 years ago
hashashini pushed to aarch64 at hashashini/tor-browser-build
5 years ago
hashashini pushed to armhf-esr60 at hashashini/tor-browser-build-nativeAarch64
5 years ago
hashashini created new branch armhf-esr60 at hashashini/tor-browser-build-nativeAarch64
5 years ago
hashashini
deleted branch arm64
at hashashini/tor-browser-build
5 years ago
hashashini pushed to aarch64 at hashashini/tor-browser-build
5 years ago
hashashini created new branch aarch64 at hashashini/tor-browser-build
5 years ago
hashashini pushed to aarch64 at hashashini/tor-browser-build-nativeAarch64
5 years ago
hashashini created new branch aarch64 at hashashini/tor-browser-build-nativeAarch64
5 years ago
hashashini pushed to master at hashashini/tor-browser-build-nativeAarch64
5 years ago
hashashini commented on issue JeremyRand/tor-browser-build#3
FYI: I made some generalizations wrt cross-compilationConcerning the use of `arch` for gcc-cross I think it would be best to use a new variable (e.g. `kernel_arch`). Apart from project/rust `arch` so far has been used in a rather different context, see my findings below. Its current use throughout upstream tor-brower-build IMO already indicates that this naming induces a certain degree of confusion.
5 years ago
hashashini pushed to armhf-esr60 at hashashini/tor-browser-build
5 years ago
hashashini pushed to armhf-esr60 at hashashini/tor-browser-build
5 years ago
hashashini pushed to armhf-esr60 at hashashini/tor-browser-build
5 years ago
hashashini pushed to armhf-esr60 at hashashini/tor-browser-build
5 years ago