I am trying to install pypy3 in TI's ARM embedded system.
It was based on linux, so I thought I could install pypy3 like I can do in linux system, but it did not work that way.
Here is what I've done:
unzip the zip file to /opt
made symlink to /usr/local/bin by ln -s opt/pypy3/bin usr/local/bin
I have checked that contents of opt/pypy3/bin are in usr/local/bin.
In each directory, libpypy3-c.so, pypy3, libpypy3-c.so.debug, and pypy3.debug exists
Then when I try pypy main.py, it doesn't work.
It just says -sh: pypy: command not found
They are the ordinary steps of installing pypy in linux.
Is there anyone who has any idea to solve this problem?
Added
When I directly run pypy3 like ./../opt/pypy3/bin/pypy3 main.py, an error message pops up says:
./../opt/pypy3/bin/pypy3: error while loading shared libraries:
libbz2.so.1.0: cannot open shared object file: No such file or
directory
What processor does the TI use? The arm downloads are based on raspberry PI or equivalent. Try the hard float one from here http://www.pypy.org/download.html
It seems you need to add the location of the pypy binary to your $PATH
Read again the sentence here "Linux binaries are only usable on the distributions written next to them". You will need to figure out how to get those dependencies on your distribution, using your OS's package manager. If you work it out, please share your solution so others can reuse it.
Related
I would like to install older versions of python for use with virtual environments, ideally from source as these versions are readily available on the official python website python 3.6 here however I can't seem to find any decent instructions.
The link above has version 3.6 full link to the tar.gz here. It downloads, I move into to program files and unzip it with 7zip:
C:\Program Files\7-Zip\7z.exe e Python-3.6.9.tgz
Then unpack the tar file:
tar -xvzf Python-3.6.9
There is no python.exe file in the unpacked directory to add to my path?
Am I missing a build step perhaps?
I found some more instructions here - where there really should be good instructions!, git is installed and setup, as is vs-code. I ran :
PCBuild\build.bat
The file 'PCBuild\pcbuild.sln' appears to have been successfully produced. Now what? I run the test described here
rt.bat -q
And I get: The system cannot find the path specified
For some reason when I run build.bat, a lot of what is printed to the seems to be mentioning python 3.8 which is now the default install on my system, its as if this method is not even pointing to the right version of python.
Please note I am looking specifically for native python approaches to this - NOT conda approaches as it is incompatible with a number of things I am doing.
I've tried; another SO queation, another SO question, here, and here, also here.
Many install guides seem to show only how to install the latest version of python using the python installer, which doesn't seem to be able to be used for legacy versions of python.
Also pythons official site has a link at the bottom labelled ' tools for unpacking archive files' which one would presume would help you to unpack, possibly even install archive files, however the link just takes you back to the top of the page?
Any help would be much appreciated?
I have been attempting to install and run pypy3 on a linux machine but am running into troubles. I have been using pypy on a mac but installed it using homebrew so didn't encounter any of these troubles.
I downloaded the most recent build and unpacked the tar file as described by their documentation. I followed the steps exactly (except replacing pypy with pypy3 and using the appropriate file name). However, when typing
./pypy3-v6.0.0-linux64/bin/pypy3
I get the following error:
./pypy3-v6.0.0-linux64/bin/pypy3: error while loading shared libraries: libbz2.so.1.0:
cannot open shared object file: No such file or directory
I'm not sure how to interpret this error. Despite the pypy documentation saying that it should run in place, pypy3 filename.py still returns the error:
If 'pypy3' is not a typo you can use command-not-found to lookup the package that
contains it, like this:
cnf pypy3
But cnf pypy3 only confirms that the pypy3 is not found.
Any help on what I'm doing wrong would be appreciated.
Those distributions are for debian linux only. You may have better luck with the portable binaries if the ones provided by OpenSuse are too old for you.
Edit: note that you used a link to an old version of the documents, you should have looked here which states "These builds depend on dynamically linked libraries that may not be available on your OS"
I am running Windows 7 64 bit and have installed easy_install. When I run easy_install from the command prompt it opens another window for the output and quickly closes before I am able to examine what has been done.
I am aware of this question but think it may have been closed prematurely as the solution that the closed ticket referred to here does not work on my system.
When I run the cmd window as Administrator and then execute (for example):
$ easy_install pip
I get the same behavior ... another cmd window flashes and then I am returned to the prompt with no output. How then do I force easy_install to output its results in the current window?
UPDATE: (additional information) This same behavior is exhibited when using pip.exe and virtualenv.exe as well. This must have something to do with how these executables are built and how they interact with windows 7 64bit.
I discovered that the issue was the version of setuptools that I was using. I had installed python-2.7.1.amd64 and then installed setuptools-0.6c12dev.win-amd64-py2.7.
In the the quest to grab a 64 bit setuptool - I failed to notice the "dev" part of the filename.
It turns out when I uninstalled it and then installed setuptools-0.6c11.win32-py2.7 all output stays in the console. There seems to be some issues with the newer "c12" version.
On a related note - this fixes the same problem with the use of pip and virtualenv as well.
Windows 7 has made user privileges a huge hassle. It's intended to protect the average user but gives developers headaches.
Run cmd.exe as Admin (right-click on the .exe and then select "Run as Administrator") and this problem should be solved.
I've also seen this happen if you install a virtualenv and then change the parent directory name. The path seems to be hardcoded in various files when you install the virtualenv, so changing anything upstream gives it fits. You can either grep/wingrep all the files that contain the path and manually update it, or do a Google search and find the "correct" way to fix the problem (I think there is one).
First try this:
Backup your Scripts\easy_install.exe to somewhere else
Go to Lib\site-packages\site-packages\distribute-0.6.13-py2.6.egg\setuptools and copy cli.exe to Scripts\, then rename it to easy_install.exe
Run and see the result.
I'm using distribute here, if you are using setuptools and the above steps doesn't work, I suggest you give distribute a try.
I had the same issue (new window behavior displayed across a number of libraries) - I believe it was the result of the compilation method used for the setuptools binary.
I had originally used the compiled binaries that were available here:
http://www.lfd.uci.edu/~gohlke/pythonlibs/
I just had to uninstall the setuptools binary and install one available here:
http://pypi.python.org/pypi/setuptools
Presumably you'd also be able to compile your own version should you need a win64 binary.
I had such problem with pip and easy_install on Windows 7. You can just use Powershell (could be found in accessories). It works fine.
i too faced the same problem once, here is an easy and quick solution
try specifying the commands like so:
c:\python27\python.exe -m easy_install Django==1.6.5v
I'm trying to get node.js running on Windows 7. I have no experience with Linux so I've just been blindly following instructions from tutorials I've found, but I'm still unable to build node.js.
What I did:
Install Cygwin - the entirety
Attempt to build node.js
This is the error I first got:
I then followed the commands of two other similar sites and they all resulted in this error (could getting several version of node have caused me more problems? I'm completely clueless on this).
I read somewhere that the Windows version of Python could be causing the problem so I uninstalled my Python 2.7 and added C:\cygwin\bin to the PATH.
That still didn't work and I read somewhere else that I'm supposed to rebaseall so I tried that, but I also got an error for that:
That's where I'm at now. Have any steps I've taken exacerbated the situation?
Add -e '/\/sys-root\/mingw\/bin/d' at line 110 in /bin/rebaseall file.
Then re-run rebaseall -v and you shouldn't get the error anymore.
See this pretty helpful blog posting - Node on CygWin doesn't work for Node v0.2.5. Use the latest v0.4.0 version instead.
Also consider the post's recommendation of compiling against MinGW instead of in CygWin.
First of all, why did you check out such an old release v0.2.5? When I did it a few weeks ago I just took the latest and ended up with 0.5.0pre, but it would also be reasonable to specify v0.4.3. For instance, type git clone git://github.com/joyent/node.git to download node, and then:
cd node
./configure
make install
Secondly, do not rebase by running ash from the CYGWIN shell. Instead, shutdown all Cygwin processes, then use Windows explorer to open the ash.exe binary. Since I have a Windows 7 system without node.js, I decided to follow my instructions and build. Not so easy. I ran into some wierd dll issues that all went away when I ran ./rebaseall followed by ./perlrebase from the ash prompt. It seems that rebaseall is not sufficient anymore.
Thirdly, there is a message that makes it sound like you don't have a C compiler. Some googling will lead you to sites telling which Cygwin packages you need, but at minimum install the g++ compiler and that should pull in C as a dependency.
When I did this I simply ran configure and every time there was an error, installed one more Cygwin package to supply the missing piece. Even OpenSSL is available.
What I just found is remove the windows based install of Python. After uninstalling this, everything is peachy.
I like cygwin a lot -- but recent releases have become pretty unreliable. Some packages just wont build, and some "standard" apps dont work e.g. gvim's "save as" bombs out on my installation.
A possible solution would be run one of the better Linux distributions (ubuntu, fedora, suse etc.) either as a virtual machine or a dual boot setup and do the build inside linux.
The question is related to the answer to "Unable to install Python without sudo access".
I need to install python-setuptools to install python modules.
I have extracted the installation package.
I get the following error when configuring
[~/wepapps/pythonModules/setuptools-0.6c9]# ./configure --prefix=/home/masi/.local
-bash: ./configure: No such file or directory
I did not find the solution at the program's homepage.
How can I resolve this error?
As Noah states, setuptools isn't an automake package so doesn't use ‘./configure’. Instead it's a pure-Python-style ‘setup.py’ (distutils) script.
You shouldn't normally need to play with .pydistutils.cfg, as long as you run it with the right version of Python. So if you haven't added the .local/bin folder to PATH, you'd have to say explicitly:
/home/masi/.local/bin/python setup.py install
AIUI this should Just Work.
I did not find the solution at the program's homepage.
Yeah, they want you to install it from a shell script egg which uses the default version of Python. Which you don't want.
(Another approach if you can't get setuptools to work is to skip it and install each module and dependency manually. Personally I have a bit of an aversion to setuptools/egg, as it contains far too much “clever” magic for my tastes and makes a mess of my filesystem. But I'm an old curmudgeon like that. Most Python modules can be obtained as simple Python files or plain old distutils scripts, but unfortunately there are some that demand eggs.)
You might want to check http://peak.telecommunity.com/DevCenter/EasyInstall#custom-installation-locations.
EasyInstall is a python module with some shell scripts (or some shell scripts with a python module?) and does not use the unix make tool that gets configured with the "./configure" command. It looks like your best bet is to try editing ~/.pydistutils.cfg to include:
[install]
install_lib = /home/masi/.local/lib/python/site-packages/
install_scripts = /home/masi/.local/bin
You'll also presumably have made the ~/.local/bin/ folder part of your PATH so you can run the easy_install script. (I'm not sure exactly where the site-packages directory will be under .local, but it shouldn't be hard to find.)
Hope this helps.