Bug 175145

Summary: lib64 used erroneously in some builds
Product: [Retired] Fedora Infrastructure Reporter: Paul W. Frields <stickster>
Component: extras buildsysAssignee: Seth Vidal <skvidal>
Status: CLOSED NOTABUG QA Contact: Jeremy Katz <katzj>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: katzj
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://www.redhat.com/archives/fedora-devel-list/2005-December/msg00194.html
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-12-13 12:36:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Paul W. Frields 2005-12-06 22:48:44 UTC
Description of problem:

Please refer to the thread at the URL above.  My FE package blogtk-1.1-4.fc4 was
built for i386 containing files where %{_libdir} evaluated to /usr/lib64. 
Replies in the thread seem to give possible solutions by changing the contents
of /etc/rpm/platform, although I am not in a position to judge whether any of
the solutions are workable for the FE build systems.

Comment 1 Paul W. Frields 2005-12-13 12:36:16 UTC
This is my fault and no one else's.  The fedora-rpmdevtools' Python spec file
template has guidance that nixes this problem.  I will revise my package to use
the template properly and that should eliminate the problem.