diff options
| author | Sam Clegg <sbc@chromium.org> | 2020-04-17 17:23:22 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-04-17 14:23:22 -0700 |
| commit | 4b04ef114a53fcaba27e9000ffb698fe898d1a37 (patch) | |
| tree | 0b9c10a8bc18876342569c936469d76c17b6b7b8 /src | |
| parent | a308fc3239091c7dbfac1530f0c70eada740fe0a (diff) | |
| download | binaryen-4b04ef114a53fcaba27e9000ffb698fe898d1a37.tar.gz binaryen-4b04ef114a53fcaba27e9000ffb698fe898d1a37.tar.bz2 binaryen-4b04ef114a53fcaba27e9000ffb698fe898d1a37.zip | |
Remove non-x86_64 architectures build from our travis config (#2777)
These have not been working since #1554, where we switch to using
an alpine docker image rather than the alpine sysroot install
script (that honors the ARCH environment variable).
So nobody has noticed in the last 2 years that we've been releasing
copies of x86_64 binaries. e.g: this file actually contains x86_64
binaries:
https://github.com/WebAssembly/binaryen/releases/download/version_91/binaryen-version_91-aarch64-linux.tar.gz
What is more its not really our job to release binaries for all these
different architectures. We can let downstream distos do that.
Node itself doesn't ship 32bit x86 linux images.
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions