Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#54876 - [emscripten] default dot file issue

Attached to Project: Community Packages
Opened by Brian Gomes Bascoy (pera) - Wednesday, 19 July 2017, 16:33 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Tuesday, 08 August 2017, 13:21 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Running emcc throws the following error message:
ERROR:root:Error in evaluating ~/.emscripten (at /home/guest/.emscripten): 'NoneType' object has no attribute 'startswith', text:
[the .emscripten file is outputted here]

Changing the config file line 11, from this:
BINARYEN_ROOT = os.path.expanduser(os.getenv('BINARYEN'))
to this:
BINARYEN_ROOT = os.path.expanduser(os.getenv('BINARYEN') or '{{{ BINARYEN_ROOT }}}')
fixed the problem.

Additional info:
* emscripten-1.37.16-1
* default ~/.emscripten

Steps to reproduce:

Run emcc after installation.
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Tuesday, 08 August 2017, 13:21 GMT
Reason for closing:  Upstream
Comment by Doug Newgard (Scimmia) - Wednesday, 19 July 2017, 16:45 GMT
And where did ~/.emscripten come from?
Comment by Brian Gomes Bascoy (pera) - Wednesday, 19 July 2017, 16:51 GMT
It was generated automatically I believe (maybe from some template, not sure). But to be more precise, these were the exact steps:
sudo pacman -S emscripten
source /etc/profile.d/emscripten.sh
emcc
emcc

The first time you run emcc it will create the ~/.emscripten file. Then the second time is when you get the error.
Comment by Doug Newgard (Scimmia) - Wednesday, 19 July 2017, 16:54 GMT
Which points to an upstream problem, not an Arch problem.
Comment by b4283 (b4283) - Sunday, 06 August 2017, 15:25 GMT
It appears that comment the line fixes the problem: "BINARYEN_ROOT = os.path.expanduser(os.getenv('BINARYEN'))" .
I'm guessing you can also fix this by installing binaryen.
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 07 August 2017, 16:02 GMT
Uh guys not sure what I'm supposed to be doing here.
Comment by Brian Gomes Bascoy (pera) - Monday, 07 August 2017, 16:29 GMT
Something is wrong with this package, compare this file (line 12): /usr/lib/emscripten/tools/settings_template_readonly.py
With this one (same line):
https://github.com/kripken/emscripten/blob/master/tools/settings_template_readonly.py

PKGBUILD runs a sed to modify that file, but I don't see how that could be introducing this issue.
Comment by Eli Schwartz (eschwartz) - Monday, 07 August 2017, 17:21 GMT
No there is nothing wrong with this package. You cannot compare the git master on Github with the tagged release version in the Arch Linux package.

Also, usptream noticed this bug and fixed it, thereby conclusively proving it was indeed... an upstream bug!
https://github.com/kripken/emscripten/commit/b67ecfbccd73f01b0252df660ad2c18471863567
Comment by Brian Gomes Bascoy (pera) - Monday, 07 August 2017, 17:49 GMT
Yeah you are right, I just quick checked the master branch and saw that file which was last modified back in March of 2016, so I assumed it was the same version being used here.

Anyways, this package is using the tag release 1.37.16, which is when this regression was introduced. Versions 1.37.17 and 1.37.18 look good.
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 08 August 2017, 13:21 GMT
Ok updated. It should be fixed then.

Loading...