dwaaan / pyrit

Automatically exported from code.google.com/p/pyrit
0 stars 0 forks source link

"-bash: pyrit: command not found" osx 10.6.6 #260

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. follow the readme install

What is the expected output? What do you see instead?

nf-MacBook:pyrit-0.3.0 Nikita$ ls
CHANGELOG   COPYING     PKG-INFO    README      cpyrit      pyrit       pyrit_cli.py    setup.py    test
nf-MacBook:pyrit-0.3.0 Nikita$ python setup.py build
svn: '.' is not a working copy
running build
running build_py
creating build
creating build/lib.macosx-10.6-i386-2.5
copying pyrit_cli.py -> build/lib.macosx-10.6-i386-2.5
creating build/lib.macosx-10.6-i386-2.5/cpyrit
copying cpyrit/__init__.py -> build/lib.macosx-10.6-i386-2.5/cpyrit
copying cpyrit/cpyrit.py -> build/lib.macosx-10.6-i386-2.5/cpyrit
copying cpyrit/util.py -> build/lib.macosx-10.6-i386-2.5/cpyrit
copying cpyrit/pckttools.py -> build/lib.macosx-10.6-i386-2.5/cpyrit
copying cpyrit/config.py -> build/lib.macosx-10.6-i386-2.5/cpyrit
copying cpyrit/network.py -> build/lib.macosx-10.6-i386-2.5/cpyrit
copying cpyrit/storage.py -> build/lib.macosx-10.6-i386-2.5/cpyrit
running build_ext
building 'cpyrit._cpyrit_cpu' extension
creating build/temp.macosx-10.6-i386-2.5
creating build/temp.macosx-10.6-i386-2.5/cpyrit
gcc-4.2 -fno-strict-aliasing -mno-fused-madd -fno-common -dynamic -DNDEBUG -g 
-fwrapv -Os -Wall -Wstrict-prototypes -DMACOSX -I/usr/include/ffi 
-DENABLE_DTRACE -arch i386 -arch ppc -pipe 
-I/System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 -c 
cpyrit/_cpyrit_cpu.c -o build/temp.macosx-10.6-i386-2.5/cpyrit/_cpyrit_cpu.o 
-DVERSION="0.3.0"
gcc-4.2 -fno-strict-aliasing -mno-fused-madd -fno-common -dynamic -DNDEBUG -g 
-fwrapv -Os -Wall -Wstrict-prototypes -DMACOSX -I/usr/include/ffi 
-DENABLE_DTRACE -arch i386 -arch ppc -pipe 
-I/System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 -c 
cpyrit/_cpyrit_cpu_sse2.S -o 
build/temp.macosx-10.6-i386-2.5/cpyrit/_cpyrit_cpu_sse2.o -DVERSION="0.3.0"
gcc-4.2 -Wl,-F. -bundle -undefined dynamic_lookup -arch i386 -arch ppc 
build/temp.macosx-10.6-i386-2.5/cpyrit/_cpyrit_cpu.o 
build/temp.macosx-10.6-i386-2.5/cpyrit/_cpyrit_cpu_sse2.o -lssl -o 
build/lib.macosx-10.6-i386-2.5/cpyrit/_cpyrit_cpu.so
running build_scripts
creating build/scripts-2.5
copying and adjusting pyrit -> build/scripts-2.5
changing mode of build/scripts-2.5/pyrit from 644 to 755
nf-MacBook:pyrit-0.3.0 Nikita$ sudo python setup.py install
svn: '.' is not a working copy
running install
running build
running build_py
running build_ext
running build_scripts
running install_lib
copying build/lib.macosx-10.6-i386-2.5/cpyrit/_cpyrit_cpu.so -> 
/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-pack
ages/cpyrit
writing byte-compilation script '/tmp/tmpSdUk04.py'
/opt/local/bin/python -O /tmp/tmpSdUk04.py
removing /tmp/tmpSdUk04.py
running install_scripts
copying build/scripts-2.5/pyrit -> 
/System/Library/Frameworks/Python.framework/Versions/2.5/bin
changing mode of 
/System/Library/Frameworks/Python.framework/Versions/2.5/bin/pyrit to 755
running install_egg_info
Removing 
/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-pack
ages/pyrit-0.3.0-py2.5.egg-info
Writing 
/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-pack
ages/pyrit-0.3.0-py2.5.egg-info
nf-MacBook:pyrit-0.3.0 Nikita$ cd 

then when trying to run

nf-MacBook:site-packages Nikita$ pyrit
-bash: pyrit: command not found

What version of the product are you using? On what operating system?

0.3.0 pyrit, Mac OS X 10.6.6

Please provide any additional information below.

Scapy and the other dependencies were installer with macports.

Original issue reported on code.google.com by nikf...@gmail.com on 12 Feb 2011 at 4:24

GoogleCodeExporter commented 8 years ago
The important line is "copying build/scripts-2.5/pyrit -> 
/System/Library/Frameworks/Python.framework/Versions/2.5/bin".

I dont know why your setup.py thinks it should install binary files to 
/System/Library/Frameworks/Python.framework/Versions/2.5/bin - the path is 
(usually) not on your $PATH and therefor the binary is not found when trying to 
execute it.

It's probably an issue caused by macports

Original comment by lukas.l...@gmail.com on 12 Feb 2011 at 8:37

GoogleCodeExporter commented 8 years ago
You were right, I was planning to reinstall osx anyways.. it works now with 
CUDA too.

This guide 
http://console-cowboys.blogspot.com/2011/01/setting-up-pyrit-on-osx.html is 
extremely helpful in avoiding macports, since I only had xCode installed at 
first.

Original comment by nikf...@gmail.com on 13 Feb 2011 at 1:57