Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running "shell:prepareLibsass" (shell) task fails: Fatal error: strderr is not defined #30

Closed
bassjobsen opened this issue May 6, 2015 · 6 comments
Labels

Comments

@bassjobsen
Copy link
Contributor

Running "shell:prepareLibsass" (shell) task
Preparing libsass version 3.2.2
  cleaning target directory
  downloading repository to target directory
Cloning into 'libsass'...
  checking out branch/tag and initializing submodules
Note: checking out '3.2.2'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at 66631c0... Merge pull request #1156 from xzyfer/feat/salt-the-earth-of-compact

Running "get-emscripten-version" task
Fatal error: strderr is not defined
@rodneyrehm
Copy link
Member

Since your output says Running "get-emscripten-version" task, I don't think it's shell:prepareLibsass that is failing. The task is trying to output strderr while it should be stderr. I fixed that in master just now. I assume you don't have emscripten installed / available in PATH.

@bassjobsen
Copy link
Contributor Author

thanks. Indeed i have to install emscripten. For some reason i expected that running npm install also installed it. I hope that building the latest version possible fixed #29

@bassjobsen
Copy link
Contributor Author

Well now i can run ./emcc -v:

~/Dropbox/testomgeving/emscripten$ ./emcc -v
WARNING  root: (Emscripten: settings file has changed, clearing cache)
INFO     root: (Emscripten: Running sanity checks)
emcc (Emscripten GCC-like replacement + linker emulating GNU ld ) 1.32.0
clang version 3.6.0 (https://github.com/kripken/emscripten-fastcomp-clang ba2eba3c4548c27b82bf945e8eba37bf630585a8) (https://github.com/kripken/emscripten-fastcomp bdf2fc7e758ee9a4594bed666d0a7a86e6e787b1)
Target: x86_64-unknown-linux-gnu
Thread model: posix
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.8
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.8.2
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.9
Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/4.9.1
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.6
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.6.4
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8.2
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9
Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9.1
Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8
Candidate multilib: .;@m64
Selected multilib: .;@m64
INFO     root: (Emscripten: Running sanity checks)

And ./emscripten:

this helps projects using emscripten find it

EMSCRIPTEN_ROOT = os.path.expanduser(os.getenv('EMSCRIPTEN') or       '/home/bass/Dropbox/testomgeving/emscripten') # directory

I still got the error mentioned above. Should i have to link emcc globally?

@bassjobsen bassjobsen reopened this May 7, 2015
@rodneyrehm
Copy link
Member

Should i have to link emcc globally?

it needs to be available in PATH, yes.

I installed emscripten via homebrew, btw. brew install emscripten --HEAD (the --HEAD option requires compiling emscripten on your system, rather than downloading binaries - this can take a while).

bassjobsen added a commit to bassjobsen/sass.js that referenced this issue May 8, 2015
@bassjobsen
Copy link
Contributor Author

Well okay, adding emscripten to the path, solves this issue.

Notice that on ubuntu i can also run sudo apt-get install emscripten which installs version 1.10.0. Running emcc --version for version 1.10.0. returns a first line with the commit nummer NOT set:
emcc (Emscripten GCC-like replacement) 1.32.0 () which means that the get-emscripten-version task fails in the first place.

Also the dependency for the closure compiler was missing, see #31

@rodneyrehm
Copy link
Member

which means that the get-emscripten-version task fails in the first place.

fixed the regex accordingly…

@rodneyrehm rodneyrehm added the bug label May 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants