I've installed Caffe on my Ubuntu 14.04 machine. the make runtest runs perfectly fine with 581 tests passed. I'm trying to work with the command line and python interface and getting the following two errors:
Command Line Interface: When I try to run the command caffe, I'm getting the following error:
No command 'caffe' found, did you mean: Command 'caff' from package
'signing-party' (universe)
caffe: command not found
Python Interface: When I run the command make pycaffe, I'm getting the following error:
CXX/LD -o python/caffe/_caffe.so python/caffe/_caffe.cpp
python/caffe/_caffe.cpp:9:31: fatal error: numpy/arrayobject.h: No such file
or directory
#include <numpy/arrayobject.h>
^
compilation terminated.
make: *** [python/caffe/_caffe.so] Error 1
Make sure that numpy is installed correctly and the path is mentioned to detect the newly installed library. The steps are provided in Caffe website itself.
For the 'Caffe' command to work, you will have to step into the folder where the 'Caffe' executable is created and then try running the executable through the terminal.
Regarding the second problem you had, I had the same problem, I solved uncommenting this line inside the Makefile.config:
# Decomment le line uncommented below:
# Homebrew installs numpy in a non standard path (keg only)
PYTHON_INCLUDE += $(dir $(shell python -c 'import numpy.core; print(numpy.core.__file__)'))/include
# PYTHON_LIB += $(shell brew --prefix numpy)/lib
Related
I'm trying to execute a python script via the macOS Automator by selecting first files and then calling the Automator workflow from my finder as can be seen in the image below.
the python file I'm trying to execute is a script that is supposed to change the file name of journal articles to a standardized format. GitHub repository
Why is it that I'm receiving the following errors when trying to use the python script on pdf files via an Automator workflow?
It seems that when using the Automator installations that come with the pubmex the pubmex.py can not be found.
for f in "$#"
do
pubmex.py $f
done
The following error is displayed:
The action “Run Shell Script” encountered an error: “zsh:3: command not found: pubmex.py”
When specifying the direct location of just the pubmex.py file another error occures.
for f in "$#"
do
/users/suntim/miniforge3/bin/pubmex.py $f
done
The following error is displayed:
The action “Run Shell Script” encountered an error: “”
When specifying the direct location of python and the pubmex.py file another error occures.
for f in "$#"
do
/usr/local/bin/python3 /users/suntim/miniforge3/bin/pubmex.py $f
done
The following error is displayed:
The action “Run Shell Script” encountered an error: “Traceback (most recent call last): File "/users/suntim/miniforge3/bin/pubmex.py", line 27, in <module> from Bio import Entrez ModuleNotFoundError: No module named 'Bio'”
I have all dependencies installed pip3 install pubmex, pip3 install biopython, brew install poppler. As it says in the readme.md that biopython should be isntalled via brew I assume that was a mistake. I instead installed it via pip3.
The same error messages occure regardless of using the zsh or bash version.
run ' python -m pip install --upgrade google-assistant-sdk[samples] ',it show below error message:
Complete output from command python setup.py egg_info:
unable to execute 'arm-poky-linux-gnueabi-gcc': No such file or directory
unable to execute 'arm-poky-linux-gnueabi-gcc': No such file or directory
No working compiler found, or bogus compiler options passed to
the compiler from Python's standard "distutils" module. See
the error messages above. Likely, the problem is not related
to CFFI but generic to the setup.py of any Python package that
tries to compile C code. (Hints: on OS/X 10.8, for errors about
-mno-fused-madd see http://stackoverflow.com/questions/22313407/
Otherwise, see https://wiki.python.org/moin/CompLangPython or
the IRC channel #python on irc.freenode.net.)
I tried to install scikits.bvp_solver on my laptop (windows 10) follow instruction here: "pythonhosted.org/scikits.bvp_solver"
I used gcc-4.8.2-32 but when I perform the command: "python setup.py config --compiler=mingw32 build --compiler=mingw32 install", it just fails with exit status 1 (See Attachment-1 below).
Then, I make an other try with pip using: "pip install scikits.bvp_solver" it gets the other error that: fail with status 1181 (LINK: fatal error LNK1181: cannot open input file 'mingw32.lib' ) (see Attachemnt-2), could any one give me advise for this case.
Attachment-1
Attachment-2
Remove *\VC\Bin\link.exe from your $PATH because you used msvc linker not mingw32.
I have the latest Anaconda Python distribution installed on Windows 8 and I am attempting to install the rpy2 package. I initially ran into several issues that I was able to circumvent but I'm now stuck on one particular error that I'm pasting below.
The command
pip install rpy2
exits with the following error message:
In file included from .\rpy\rinterface\_rinterface.c:58:0:
.\rpy\rinterface\_rinterface.h:8:15: fatal error: R.h: No such file or
directory
compilation terminated.
error: command 'gcc' failed with exit status 1
Any suggestions? The path to R.h is included on my environment.
Dr. Gohlke's binary is probably the easiest solution. But you need to change the Python installation path in your registry for this method to work. The relevant key is in HKEY_LOCAL_MACHINE\SOFTWARE\Python\PythonCore\2.7\InstallPath. Change it so that the anaconda Python is the default python installation. You can always change it back if you want.
So I'm in the PyQT folder that I just downloaded and unzipped, and am trying to run configure.py. I'm doing this
alexandermoreno$ python configure.py -q /users/alexandermoreno/QT/5.2.1/clang_64/bin/qmake -d /Library/Python/2.7/site-packages/ --use-arch x86_64
giving me the following error:
-bash: python configure.py -q : command not found
However, when I run python configure.py just to see its output, I get:
Error: Make sure you have a working Qt qmake on your PATH or use the -q
argument to explicitly specify a working Qt qmake.
So it's saying to use the -q file, but then when I use it, it gives me that the command is not found.