Fwiw: Unless there is something that acts on `rustc --print target-list` without applying some human judgement first, I would rather we just reassigned this bug to LLVM and enabled wasm. "Fixing" this in rustc, and then unfixing it again once we add support to LLVM seems a little bit like chasing our tails...
Ditto for other cross-compile targets (windows, android, etc) that are reported in `target-list` but don't _actually_ work due to other missing parts of the toolchain. - Gus On Fri, 6 Jul 2018 at 19:39 Niels Langager Ellegaard < niels.langager.ellega...@greve-gym.dk> wrote: > > Package: rustc > Version: 1.26.2+dfsg1-1 > Severity: minor > > Dear Maintainers, > > The wasm32-unknown-unknown target is enabled in rustc, but it doesn't > work. > Alledgedly the problem is that the coresponding webassembly target isn't > enabled in > llvm. I guess that the target should be disabled in rustc if it doesn't > work. > (But in the long run it would be great to have the target enabled) >
