# Need help with emscripten port

**URL:** <https://internals.rust-lang.org/t/need-help-with-emscripten-port/3154>\
**Category:** Uncategorized\
**Created:** [February 8, 2016, 10:37pm UTC](https://internals.rust-lang.org/t/need-help-with-emscripten-port/3154 "2016-02-08T22:37:00Z")\
**Posts on this page:** 1\
**Showing post:** 124

<div class="post-metadata">

**Author:** ![brson](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/brson/32/5197_2.png) [@brson](https://internals.rust-lang.org/u/brson)\
**Post date:** [September 29, 2016, 10:18pm UTC](https://internals.rust-lang.org/t/need-help-with-emscripten-port/3154/124 "2016-09-29T22:18:42Z")

</div>

There’s a [significant setback](https://github.com/rust-lang/rust/pull/36339#issuecomment-250046084) to landing the emscripten PR. The mingw build is creating some suspicious linker errors. As far as I can tell the symbols it is complaining about exist, so I have no idea what is going on. My best wild guess is some bug in the mingw linker due to the increased binary size from the fastcomp backend.

Unless anybody has other ideas, one thing we might do to attempt to address this is to make the port work without the fastcomp backend. As I [mentioned previously](https://internals.rust-lang.org/t/need-help-with-emscripten-port/3154/114?u=brson) it shouldn’t actually be required in order for us to output the correct bitcode for emcc to use.

---

_[View the full topic](https://internals.rust-lang.org/t/need-help-with-emscripten-port/3154)._