Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 713590 - AntTweakBar-1.14-1 not built with $RPM_OPT_FLAGS
Summary: AntTweakBar-1.14-1 not built with $RPM_OPT_FLAGS
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: AntTweakBar
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Sean Middleditch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: DebugInfo
TreeView+ depends on / blocked
 
Reported: 2011-06-15 20:46 UTC by Ville Skyttä
Modified: 2011-06-16 08:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-15 21:59:22 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Ville Skyttä 2011-06-15 20:46:30 UTC 
AntTweakBar-1.14-1 is not built with $RPM_OPT_FLAGS:
http://kojipkgs.fedoraproject.org/packages/AntTweakBar/1.14/1.fc16/data/logs/x86_64/build.log

1.13-6 did not have this problem:
http://kojipkgs.fedoraproject.org/packages/AntTweakBar/1.13/6.fc15/data/logs/x86_64/build.log

grepping through the 1.14 source tarball I find nothing related to FEDORA_CXXFLAGS.  Setting CXXCFG instead of it might fix it (untested).
Comment 1 Sean Middleditch 2011-06-15 21:59:22 UTC 
Huh.  I didn't change the build setup at all, so it's strange that it would have worked right in the old version.  I pushed a 1.14-2 that fixes this issue.
Comment 2 Ville Skyttä 2011-06-16 05:31:47 UTC 
(In reply to comment #1)
> Huh.  I didn't change the build setup at all,

The AntTweakBar-makefile.patch which was in 1.13-6 had stuff related to FEDORA_CXXFLAGS.
Comment 3 Sean Middleditch 2011-06-16 08:55:41 UTC 
Ah.  Well now I just feel silly, since I wrote that patch.  :)  Setting the proper variable for the build system in the spec file makes more sense anyway though, at least.
Note You need to log in before you can comment on or make changes to this bug.