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

Error installing from source with pych -k #98

Open
buddha314 opened this issue Apr 3, 2018 · 3 comments
Open

Error installing from source with pych -k #98

buddha314 opened this issue Apr 3, 2018 · 3 comments

Comments

@buddha314
Copy link

Installed from source. Stayed as close to this as possible: http://pychapel.readthedocs.io/en/latest/introduction.html

pych -k
ERROR:__init__:<module>: If you are installing just now, then ignore this error message: Could not find config-file(pych.json), check your installation or try re-installing.
ERR: Cannot find configuration file (pych.json).

With this

printchplenv 
machine info: Darwin macbuddha.lan 16.7.0 Darwin Kernel Version 16.7.0: Mon Nov 13 21:56:25 PST 2017; root:xnu-3789.72.11~1/RELEASE_X86_64 x86_64
CHPL_HOME: /Users/buddha/github/chapel *
script location: /Users/buddha/github/chapel/util
CHPL_TARGET_PLATFORM: darwin
CHPL_TARGET_COMPILER: clang
CHPL_TARGET_ARCH: native
CHPL_LOCALE_MODEL: flat
CHPL_COMM: none
CHPL_TASKS: qthreads
CHPL_LAUNCHER: none
CHPL_TIMERS: generic
CHPL_UNWIND: none
CHPL_MEM: jemalloc
CHPL_ATOMICS: intrinsics
CHPL_GMP: gmp
CHPL_HWLOC: hwloc
CHPL_REGEXP: re2
CHPL_AUX_FILESYS: none
@lydia-duncan
Copy link
Member

This repository has portability issues, see #46 - there's a work-around for Macs, but it hasn't been promoted to the repository yet

@buddha314
Copy link
Author

That last comment says it no longer works. All right, when do we expect this ticket closed?

@lydia-duncan
Copy link
Member

I think he meant the script to install it in one command no longer works. The patch to allow it to build with the extensive steps probably is still fine.

As for when I expect this ticket to close: it'll depend on the result of my work. If we need to significantly rework the python interoperability approach, it'll likely be further out (and likely involve a new project). I'm still getting ramped up so I don't have a good estimate yet, sorry

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants