Mismatched tools in macOS emsdk.

[キャロウ マーク]

I get the following error from `emcc -v`.

shared:ERROR: Emscripten, llvm and clang build versions do not match, this is dangerous (1.38.33, 1.38.31, 1.38.31)

I did the following as instructed by emscripten.org:

git clone https://github.com/emscripten-core/emsdk.git

cd emsdk

git pull

./emsdk install latest

./emsdk activate latest

source ./emsdk_env.sh

emcc -v

Did I do something wrong or is the macOS version of the SDK broken?

There are some issues with the instructions:

1. It says the mac 10.3.3 or later should have a new enough version of Python. It doesn’t. I have 10.14.5 and the /System Python version is 2.7.10. emsdk insists on 2.7.12.
2. The directions for installing the Xcode command line tools tell you to go to Xcode | Preferences | Downloads. There is no such place in Preferences. From the GUI you pick Open Developer Tool | More Developer Tools … from the Xcode menu. From the command line you can do  `xcode-select —install` for which you apparently don’t need Xcode installed.
3. It tells you to download and install git from git-scm.com. But if you’ve installed the Xcode command line tools, you already have git. So why is this needed?

Does emsdk work with Python3?

Regards

    -Mark

[Alon Zakai]

The first two issues, the emscripten version error and the python version error, have been fixed on incoming, so tagging a new release should resolve them. I opened https://github.com/emscripten-core/emsdk/pull/258 to do that now.

The other issues do sound like things we need to update in our MacOS docs. Perhaps you can open a PR? (I don't have a Mac myself, not sure what to write.)

The emsdk should work with python 3, we do have testing for it on CI as of recently even. Have you seen a problem?

- Alon

--
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 emscripten-disc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/6DF04A52-17A3-4D20-9DA1-955841964744%40callow.im.
For more options, visit https://groups.google.com/d/optout.

[Floh]

...regarding the python version confusion on macOS:

The preinstalled python version on macOS is indeed stuck at 2.7.10, even in the latest macOS Mojave Beta. This will most likely never be updated, but AFAIK the pre-installed python version also isn't really recommended for general use.

Instead use brew to install an uptodate python2 version:

> brew install python@2

This will override the system python version on the command line:

> which python

/usr/local/bin/python

> python --version

Python 2.7.16

Note that "brew install python" will install the latest python 3.x version, but as "python3" command so that it doesn't clash with any python 2.7.x versions. Only doing this will still run the outdated 2.7.10 version when running "python" on the command line.

Cheers,

-Floh.

To unsubscribe from this group and stop receiving emails from it, send an email to emscripten-discuss+unsub...@googlegroups.com.

[キャロウ マーク]

On Jun 1, 2019, at 19:49, Alon Zakai <alon...@gmail.com> wrote:

The first two issues, the emscripten version error and the python version error, have been fixed on incoming, so tagging a new release should resolve them. I opened https://github.com/emscripten-core/emsdk/pull/258 to do that now.

The other issues do sound like things we need to update in our MacOS docs. Perhaps you can open a PR? (I don't have a Mac myself, not sure what to write.)

The emsdk should work with python 3, we do have testing for it on CI as of recently even. Have you seen a problem?

Thanks for the fix. I’ve just pulled and installed latest. I can confirm that all tool versions are now 1.38.31 and that emcc is happy with Python 2.7.10. I’ll open a PR soon to fix the macOS docs. I want to make sure I have everything working properly before I do that. I hadn't tried Python 3 with emcc. I was being curious. I have now tried emcc -v with it. It works.

Regards

    -Mark

[キャロウ マーク]

> On Jun 3, 2019, at 5:53, Floh <flo...@gmail.com> wrote:
>
> ...regarding the python version confusion on macOS:
>
> The preinstalled python version on macOS is indeed stuck at 2.7.10, even in the latest macOS Mojave Beta. This will most likely never be updated, but AFAIK the pre-installed python version also isn't really recommended for general use.
>
> Instead use brew to install an uptodate python2 version:
>
> > brew install python@2
>
> This will override the system python version on the command line:
>
> > which python
> /usr/local/bin/python
> > python --version
> Python 2.7.16
>
> Note that "brew install python" will install the latest python 3.x version, but as "python3" command so that it doesn't clash with any python 2.7.x versions. Only doing this will still run the outdated 2.7.10 version when running "python" on the command line.
>

Thanks for the reply. Alon has fixed Emscripten so it no longer insists on 2.7.12 and works with 2.7.10.

Actually the pre-installed 2.7.10 is just the same as any other 2.7.10, except that it already includes PyObjC rather than requiring an additional download. I’ve been using it and its predecessors for a long time without any problem. I don’t know why it would not be recommended for general use.

I actually already had a MacPorts distribution of Python2 installed. It was 2.7.10 as well and not installed all that long ago. I have updated to the latest MacPorts version which is 2.10.16 like Brew. Not the very latest available but close enough. But I’ll probably continue to default to the pre-installed Python.

Regards

-Mark