Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 80481

Summary: rebuild of freetype srpm with bytecode interpreter on fails.
Product: [Retired] Red Hat Public Beta Reporter: Nick Uniatowski <nicku>
Component: freetypeAssignee: Owen Taylor <otaylor>
Status: CLOSED NOTABUG QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: phoebe   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-12-27 22:05:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Nick Uniatowski 2002-12-27 01:48:27 UTC
Description of problem:
Rebuild of i386 binaries of freetype 2.1.2 for i386 fails after enabling the
bytecode interpreter.

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

How reproducible:

Steps to Reproduce:
1. set '%define without_bytecode_interpreter    0'
2. rpmbuild -bb freetype.spec
Actual results:
install -m 755 ft2demos-2.1.2/bin/.libs/ftview
+ /usr/lib/rpm/redhat/ /var/tmp/freetype-2.1.2-root freetype
No translations found for freetype in /var/tmp/freetype-2.1.2-root
error: Bad exit status from /var/tmp/rpm-tmp.54166 (%install)

Expected results:
proper binary rpm

Additional info:

Comment 1 Owen Taylor 2002-12-27 22:05:59 UTC
We'll be upgrading to 2.1.3 at some point, at which point I'll fix it
if it's currently broken in Rawhide. Not clear to me offhand what
the problem you are running into is; that part of the spec file looks

My best guess here would be that perhaps you have the LINGUAS environment
variable set or for some other reason translations are not getting

I generally wouldn't consider "does not rebuild" problems to be worth
filing, unless you debug them and there is something interesting going
on. We periodically run mass-rebuild tests to catch stuff that isn't