Bug 147622 - Pyzor fails to build on x86_64
Pyzor fails to build on x86_64
Product: Fedora
Classification: Fedora
Component: pyzor (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Warren Togami
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2005-02-09 16:22 EST by Toshio Kuratomi
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-02-09 22:10:42 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch to fix building on x86_64 (3.98 KB, patch)
2005-02-09 16:27 EST, Toshio Kuratomi
no flags Details | Diff

  None (edit)
Description Toshio Kuratomi 2005-02-09 16:22:07 EST
Description of problem:
pyzor fails to build on x86_64.  This is due to the use of %{_libdir} in the
files section which searches for the installed files under /usr/lib64 on x86_64.
 because the files are arch independent python files, they are installed under
/usr/lib on multilib.  Using the latest macros from fedora-rpmdevtools
spectemplate.python fixes this.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. On an x86_64 computer, rombuild -ba pyzor.spec
Actual results:
See buildlog:

Expected results:
Produce an rpm package file.

Additional info:
Comment 1 Toshio Kuratomi 2005-02-09 16:27:06 EST
Created attachment 110896 [details]
Patch to fix building on x86_64

This patch updates the python macros to what's in fedora-rpmdevtools-0.3.0-1. 
They resolve the build problem by using the python_sitearch macro instead of
_libdir.  This patch is slightly different than the version tested by Aurelian
Bompard [1]_ as I also ghosted the pyzor .pyo files.

Comment 2 Warren Togami 2005-02-09 22:10:42 EST
Thanks Toshio.  Lately I've seriously been considering sponsoring you.
 Keep it up.

Note You need to log in before you can comment on or make changes to this bug.