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.

Sign up for GitHub

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

Jump to bottom

Example does not work on Linux amd64 #38

Closed
deepankarsharma opened this issue Feb 17, 2016 · 6 comments
Closed

Example does not work on Linux amd64 #38

deepankarsharma opened this issue Feb 17, 2016 · 6 comments

Comments

@deepankarsharma
Copy link

Get this error ->
python -m peachpy.x86_64 -mabi=sysv -mimage-format=elf -o matmul.o matmul-opt.py
/usr/bin/python: No module named avx; 'peachpy.x86_64' is a package and cannot be directly executed

Also running make gives this ->
user@ne:~/Downloads/PeachPy-master/examples/make$ make
python -m peachpy.x86_64 -MMD -MF matmul-opt.d -o matmul-opt.o matmul-opt.py
/usr/bin/python: No module named avx; 'peachpy.x86_64' is a package and cannot be directly executed
Makefile:12: recipe for target 'matmul-opt.o' failed
make: *** [matmul-opt.o] Error 1

This is on ubuntu wily with built in Python 2.7.10.
@Maratyszcza
Copy link
Owner

It seems that you didn't generate the instruction classes. See installation instructions

@deepankarsharma
Copy link
Author

User error :) Example works once I followed the instructions.

@Maratyszcza
Copy link
Owner

Thanks, I close the issue then

@pwaller
Copy link
Contributor

pwaller commented Dec 4, 2016

I just hit this. This is not user friendly. Is there a good reason to break pip install git+https://github.com/Maratyszcza/PeachPy? If I want to tell a user or developer to install peachpy so that they can build things I write, I would hope peachpy is really be as simple as possible to install (and follow the standard way all other python modules are built). Telling the users they have to come and read your README before they can get started with mine is not ideal. I don't want to write the installation instructions for peachpy in my README either, because they might go out of date in time.

@Maratyszcza
Copy link
Owner

@pwaller I'm not an expert on Python packing, but it seems that you are. If you could fix it and submit a PR, it would be a welcome contribution!

pwaller added a commit to pwaller/Opcodes that referenced this issue Dec 4, 2016
@pwaller
Use setuptools to locate XML to read
68c118c 
This makes the code compatible with opcodes being packaged up as an .egg
file, which is required for supporting

It also makes setuptools a requirement for installing the package. This
should probably be documented.

This is part of making PeachPy easy to install by making the code
generation happen automatically during installation time (see
Maratyszcza/PeachPy#38).
@pwaller pwaller mentioned this issue Dec 4, 2016
Closed
pwaller added a commit to pwaller/Opcodes that referenced this issue Dec 4, 2016
@pwaller
Use setuptools to locate XML to read
3ac7da4 
This makes the code compatible with opcodes being packaged up as an .egg
file, which is required for supporting

It also makes setuptools a requirement for installing the package. This
should probably be documented.

This is part of making PeachPy easy to install by making the code
generation happen automatically during installation time (see
Maratyszcza/PeachPy#38).
pwaller added a commit to pwaller/Opcodes that referenced this issue Dec 4, 2016
@pwaller
Use setuptools to locate XML to read
1ae81fb 
This makes the code compatible with opcodes being packaged up as an .egg
file, which is required for supporting

It also makes setuptools a requirement for installing the package. This
should probably be documented.

This is part of making PeachPy easy to install by making the code
generation happen automatically during installation time (see
Maratyszcza/PeachPy#38).
Maratyszcza pushed a commit to Maratyszcza/Opcodes that referenced this issue Dec 5, 2016
@pwaller @Maratyszcza
Use setuptools to locate XML to read
653f470 
This makes the code compatible with opcodes being packaged up as an .egg
file, which is required for supporting

It also makes setuptools a requirement for installing the package. This
should probably be documented.

This is part of making PeachPy easy to install by making the code
generation happen automatically during installation time (see
Maratyszcza/PeachPy#38).
@pwaller
Copy link
Contributor

pwaller commented Dec 5, 2016

In case anyone is reading this, it was resolved in #61.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pwaller @deepankarsharma @Maratyszcza