cannot install on os x #45
Comments
|
i forgot to mention: in summary, currently NONE of the various install options works for me! could you please look into this? |
|
I could not reproduce the problem on macOS Sierra or High Sierra - the X development environment on your host is probably broken. We will provide a Python wheel as soon as possible - this will make the installation much easier and faster. We did already similar thing for Julia and it works fine on all platforms. As a temporary workaround, you can download http://gr-framework.org/downloads/gr-latest-Darwin-x86_64.tar.gz, extract it in your home directory and set the Python path, e.g. tar -C ${HOME} -xf ~/Downloads/gr-latest-Darwin-x86_64.tar.gz
export GRDIR=${HOME}/gr
export PYTHONPATH=${PYTHONPATH}:${GRDIR}/lib/python |
|
thanks for your help. there may be something that's broken but i do use homebrew successfully with this setup; the latest xcode command line tools are installed. also, anaconda is installed. just for reference, here is some of my |
|
oh, and the direct unzipping installation works! i'm looking forward to using gr! |
|
For Julia, we have a http-fallback for the download. On some (older) Linux systems, users complained about similar download problems - but, on macOS I never heard about certificate failures. For any reason, the CA bundle on your Mac seems to be out-of-date ... Could you download the tar-file with curl or wget (using the secure way via https) ? |
|
sorry if there was a confusion: downloading the linked tar file works without problems; just the pip installation runs into this certificate error (described in the other issue). no idea what's wrong. could it be that my anaconda installation is too old? ah, now i get it: the question if i can use https at all... will try. |
|
|
|
I suppose you are using Anaconda Python? Could you please test the Python download: pip download https://gr-framework.org/downloads/gr-latest-Darwin-x86_64.tar.gz |
|
Anaconda's |
|
for the pip download i get so at least the download itself works |
|
i am having troubles again... basically the situation has actually deteriorated since last time, as i have no working current gr installation once more :( i now have a fresh install of anaconda2. again i tried various ways of installing gr, without much success. still on OS X sierra. gives GR runtime not found. i verified that i also tried |
|
next, i downloaded this lets me successfully locate this may be a bug in where the DLL is searched? to my eye it seems like the last part of that path should be |
|
finally, i reset the environment variables as a side note, |
|
Hello Nils,
With the GR runtime downloaded from the tarball placed in |
|
Strange! I checked the installation on a fresh macOS system:
|
|
@FlorianRhiem yes thanks. i think it's a great idea to separate the repositories and the packages. i downloaded the whole thing only because last time that was the only installation method that worked for me... but good to know that this will soon not be possible. |
|
Just to confirm, is everything working for you now? The automated download of the GR runtime via HTTPS seems to fail on some systems, so we will switch to download via HTTP and verify the downloaded file's hash, in the hope that this will solve issues like yours in the future without requiring anything other than |
|
Ah, I remember. There is no error message, right? |
|
i tried now again by setting anyway, i then did |
|
(to be clear the manually downloaded tarball ist still in place in |
|
Do you still have |
|
yes, that was what was missing. success! so out of curiosity, where does the auto-download try to put GR? will it always be necessary to set these variables? |
|
also please note that the https download succeeds for me! still the pure pip installation fails. as i commented above... |
|
specifically, as i wrote here: i also tried anyway thanks for now, it's working currently! |
|
Great :) The automatic download will install the files along with the python package. Usually, there is no need to set any environment variables at all. The download is done using urlopen. What version of |
|
it's a fresh current anaconda. i get pip 9.0.1 . in python i can |
|
Hm, thanks. I'm stumped on what might cause problems other than the download, but I would suggest that we leave it at that for today, since everything is working for you. |
|
i just tried; i import urlopen from urllib2 and when i type i get no 404 error but some |
|
and if i do |
|
actually, on os x, having brew install gr would also be a viable option i think. (just for the non-python part) |
|
Okay, if the download works, the files get lost somewhere else along the way. Could you please Please post the complete output here. If one of the steps fails, stop and post the output until then. |
|
ok, i've done that and appended all the outputs into one file. |
|
Thank you! Everything looks correct, the libraries (e.g. libGR.so) are all there. Is it possible to |
|
@FlorianRhiem ok, so what i did now is uninstall the pip-installed version, unset the environment variables, run python setup.py install as above to be sure. i can then successfully import and run gr. |
|
so it seems the pip installation fails somewhere between the download and the install?? |
|
Yes, though I'm not sure what could cause that. The next step would be to Also, what exactly does the output of There should be a brief delay during |
|
to be sure: what is the initial state i need before i run |
|
For running |
|
ok, but are already manually downloaded or installed artefacts a problem? (that's what i have right now) |
|
No, just make sure to |
|
hmm this does not seem to download anything: i did |
|
weird? it looks as if the gr runtime was found nonetheless? |
|
Update: If the GR runtime is found, you can check which is found by doing the following: that will return something like this: Judging by the output,
We do not upload wheels at the moment as we will not be able to provide them for Linux (the various distributions vary too greatly when it comes to using X11 and other libraries), but it should be doable to provide wheels for macOS. I will have to discuss that with the other developers and it probably will take some time due to the holidays. I hope the |
|
hi, so i did however, this only works if i run python from an environment where GRLIB and GRDIR are set. if i instead run |
|
so what's weird is that in the pip install step somehow even without working |
|
The availability of the GR runtime is checked when gr is being built, but that step does not seem to happen on your system at all. Without being built, the Python package cannot work correcty without additional "help" from the user, like manually setting up the GR runtime and the environment variables. |
|
i see. here is the output of |
|
there is some cached wheel it seems?! should i delete that to try again? how? |
|
Ah, that does help! So |
|
ok! did that. |
|
with this install i can import gr and successfully draw a line! nice! this now works without it could be that my former troubles were all caused by some cache giving a non functional version.. |
|
actually i concatenated the output files by accident ( |
|
That leaves the question what has changed between now and when the broken wheel was created. At least now we know it works as intended. :) Feel free to close the issue. |
|
well, that's hard to know now after the fact. i think it can be closed for now. thanks again! |
|
i just noticed another possible culprit: i was running ipython inside tmux. apparently tmux also has a caching mechanism for environment variables or something of the kind. in short, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
hi, i tried two methods as described on the home page:
conda install grworks but installs the old version 0.18. i then uninstalled that again.conda --versiongives 4.3.25.pip install gr. mypipis the one from anaconda since the paths are set up that way. however, this installation fails during build. here is a snippet of the output:and the output ends with
my gcc is this:
how can i install a recent version of gr on a current os x system?
The text was updated successfully, but these errors were encountered: