Skip to content

Instantly share code, notes, and snippets.

@ShonFrazier
Created January 11, 2021 20:47
Show Gist options
  • Save ShonFrazier/11d1200477e7c9eeda7cfcd93137eae5 to your computer and use it in GitHub Desktop.
Save ShonFrazier/11d1200477e7c9eeda7cfcd93137eae5 to your computer and use it in GitHub Desktop.
emscripten on macOS 10.15.7 - Homebrew build logs
Homebrew build logs for emscripten on macOS 10.15.7
Build date: 2021-01-11 15:26:17
HOMEBREW_VERSION: 2.7.3-3-gb29c27b
ORIGIN: https://github.com/Homebrew/brew
HEAD: b29c27b9a8e400ea696cb78f45fc2d7fb2a7ad28
Last commit: 4 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 3cc0c737e682f1ad68fa85ac5e2d12ef83b0f952
Core tap last commit: 66 minutes ago
Core tap branch: master
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CASK_OPTS: []
HOMEBREW_EDITOR: /usr/local/bin/vim
HOMEBREW_GITHUB_API_TOKEN: set
HOMEBREW_MAKE_JOBS: 16
Homebrew Ruby: 2.6.3 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3_2/bin/ruby
CPU: 16-core 64-bit skylake
Clang: 12.0 build 1200
Git: 2.30.0 => /usr/local/bin/git
Curl: 7.64.1 => /usr/bin/curl
Java: 14.0.1, 10.0.1
macOS: 10.15.7-x86_64
CLT: 12.3.0.0.1.1607026830
Xcode: 12.3
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!
Warning: "config" scripts exist outside your system or Homebrew directories.
`./configure` scripts often look for *-config scripts to determine if
software packages are installed, and which additional flags to use when
compiling and linking.
Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew-provided
script of the same name. We found the following "config" scripts:
/Users/shon/.pyenv/shims/python3.9-config
/Users/shon/.pyenv/shims/powerline-config
/Users/shon/.pyenv/shims/python-config
/Users/shon/.pyenv/shims/python3-config
2021-01-11 15:44:28 -0500
/usr/local/Cellar/emscripten/2.0.12/bin/emcc
emcc: error: no input files
HOMEBREW_VERSION: 2.7.3-3-gb29c27b
ORIGIN: https://github.com/Homebrew/brew
HEAD: b29c27b9a8e400ea696cb78f45fc2d7fb2a7ad28
Last commit: 4 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 3cc0c737e682f1ad68fa85ac5e2d12ef83b0f952
Core tap last commit: 63 minutes ago
Core tap branch: master
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CASK_OPTS: []
HOMEBREW_EDITOR: /usr/local/bin/vim
HOMEBREW_MAKE_JOBS: 16
Homebrew Ruby: 2.6.3 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3_2/bin/ruby
CPU: 16-core 64-bit skylake
Clang: 12.0 build 1200
Git: 2.30.0 => /usr/local/bin/git
Curl: 7.64.1 => /usr/bin/curl
Java: 14.0.1, 10.0.1
macOS: 10.15.7-x86_64
CLT: 12.3.0.0.1.1607026830
Xcode: 12.3
HOMEBREW_GIT: git
PATH: /Users/shon/.nix-profile/bin:/Users/shon/.pyenv/shims:/usr/local/opt/terraform@0.11/bin:/usr/local/opt/llvm/bin:/Users/shon/.bin:/Users/shon/.cargo/bin:/usr/local/bin:/usr/local/lib:/usr/local/sbin:/usr/libexec:/Users/shon/go/bin:/usr/local/opt/python/libexec/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/usr/local/share/dotnet:~/.dotnet/tools:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Library/TeX/texbin
2021-01-11 15:27:45 -0500
/usr/local/Cellar/emscripten/2.0.12/bin/emcc
test.c
-o
test.js
-s
NO_EXIT_RUNTIME=0
==============================================================================
Welcome to Emscripten!
This is the first time any of the Emscripten tools has been run.
A settings file has been copied to /private/tmp/emscripten-test-20210111-6197-1acn10y/.emscripten, at absolute path: /private/tmp/emscripten-test-20210111-6197-1acn10y/.emscripten
It contains our best guesses for the important paths, which are:
LLVM_ROOT = /usr/local/opt/llvm/bin
NODE_JS = /usr/local/bin/node
EMSCRIPTEN_ROOT = /usr/local/Cellar/emscripten/2.0.12/libexec
Please edit the file if any of those are incorrect.
This command will now exit. When you are done editing those paths, re-run it.
==============================================================================
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment