I think this is know issue: https://github.com/emscripten-core/emsdk/issues/385
I imagine the fix could be easy, but we also want to think about the right approach for how to support such polyglot configuration. e.g. windows python + running in msys2 sh.exe msys2 python + running in cmd.exe It gets even more complicated if you try to run an autoconf script: https://github.com/emscripten-core/emscripten/issues/12376. Specifically, it's not clear to me how to setup the emsdk environment such that it work in all cases. Do we set EMSDK_BLAH=c:\blah or EMSDK_BLAH=/c/blah? I imagine msys2 has solutions to this problem but I'm not at a familiar with it Help would be very much appreciated! Ideally we would add testing for all this stuff to emsdk and maybe some minimal tests in emscripten. A quick fix patch could also work if you'd like to propose one. cheers, sam On Wed, Sep 30, 2020 at 2:03 AM Arthur Norman <[email protected]> wrote: > > I see from a year back that the core team do not have time to check > installation on all possible setups, specifically cygwin and myss2, and > that for Windows testing they maybe look to WSL. My main work has used > Cygwin fo rmany years and having WSL activated risks confusion and conflict > for me, so I do not see it as a good option - and even more so if I wanted > to include emscripten stuff in my main project. > When I try a fresh install on cygwin (or mysys2) I get a failure > > Traceback (most recent call last): > File "./emsdk.py", line 3055, in <module> > sys.exit(main()) > File "./emsdk.py", line 2799, in main > load_sdk_manifest() > File "./emsdk.py", line 2338, in load_sdk_manifest > add_sdk(sdk) > File "./emsdk.py", line 1972, in add_sdk > raise Exception('Duplicate sdk ' + str(sdk) + '! Existing:\n{' + ', > '.join("%s: %s" % item for item in vars(find_sdk(str(sdk))).items()) + '}, > New:\n{' + ', '.join("%s: %s" % item for item in vars(sdk).items()) + '}') > Exception: Duplicate sdk sdk-upstream-master-64bit! Existing: > {version: upstream-master, bitness: 64, uses: ['llvm-git-master-64bit', > 'node-12.18.1-64bit', 'python-3.7.4-pywin32-64bit', > 'emscripten-master-64bit', 'binaryen-master-64bit'], os: win, id: sdk, > name: sdk-upstream-master-64bit, is_old: False, is_sdk: True}, New: > {version: upstream-master, bitness: 64, uses: ['llvm-git-master-64bit', > 'node-12.18.1-64bit', 'emscripten-master-64bit', 'binaryen-master-64bit'], > os: linux, id: sdk, name: sdk-upstream-master-64bit, is_old: False, is_sdk: > True} > > which looks as if the script is confused as between Windows and Linux (and > we can all se that that is reasonable!). > > So my questions > Is there experience or expectation that if I get past installation that > emscripten will work under cygwin? > > If not then I should avoid wating my time. But if this ia liable to be > fairly shallow I can investigate further and hope to report back with any > patch or fix I find. So either is there somebody with a solution already or > will following up on this be a good use of my time or a rabbit-hole of > unlimited depth? > > Arthur > > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/emscripten-discuss/23852e32-f3c1-4bcf-a985-407ba91e388en%40googlegroups.com > <https://groups.google.com/d/msgid/emscripten-discuss/23852e32-f3c1-4bcf-a985-407ba91e388en%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/CAL_va2__o6nJwm24h9%2BKGcdfpxaPRjOYHZT16if2V2%2BuDWgwWw%40mail.gmail.com.
