Bug 735594 - openni 1.3.2.1-0.1.gitf8467404 not built with $RPM_OPT_FLAGS
openni 1.3.2.1-0.1.gitf8467404 not built with $RPM_OPT_FLAGS
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: openni (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Tim Niemueller
Fedora Extras Quality Assurance
: Patch, Regression
Depends On:
Blocks: DebugInfo
  Show dependency treegraph
 
Reported: 2011-09-03 14:41 EDT by Ville Skyttä
Modified: 2011-12-31 15:25 EST (History)
1 user (show)

See Also:
Fixed In Version: openni-primesense-5.0.3.3-1.fc16
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-12-31 15:25:45 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
Build with $RPM_OPT_FLAGS, include build commands in build output (503 bytes, patch)
2011-09-03 14:41 EDT, Ville Skyttä
no flags Details | Diff

  None (edit)
Description Ville Skyttä 2011-09-03 14:41:40 EDT
Created attachment 521338 [details]
Build with $RPM_OPT_FLAGS, include build commands in build output

openni 1.3.2.1-0.1.gitf8467404 is not built with $RPM_OPT_FLAGS; the sed that tries to get that done is outdated (and unnecessary).

The attached patch seems to fix it, and also adds $RPM_LD_FLAGS for [1].  I didn't find evidence of DEBUG=1 having any effect, but I left it in in any case.  The "cat" is there so it is possible to look at the build output to see if things are being built as expected, I recommend leaving it in.

[1] https://fedoraproject.org/wiki/FWN/Issue283#New_hardened_build_support_.28coming.29_in_F16
Comment 1 Tim Niemueller 2011-10-11 18:30:29 EDT
Thanks for this info, nice catch! I have updated the master spec file. I'll issue updates soon, still fighting with some openni-primesense problems.
Comment 2 Fedora Update System 2011-10-27 15:02:08 EDT
openni-1.3.2.1-0.2.gitf8467404.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/openni-1.3.2.1-0.2.gitf8467404.fc16
Comment 3 Fedora Update System 2011-10-27 15:02:53 EDT
openni-1.3.2.1-0.2.gitf8467404.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/openni-1.3.2.1-0.2.gitf8467404.fc15
Comment 4 Fedora Update System 2011-10-27 15:03:42 EDT
openni-1.3.2.1-0.2.gitf8467404.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/openni-1.3.2.1-0.2.gitf8467404.fc14
Comment 5 Fedora Update System 2011-10-29 20:27:25 EDT
Package openni-1.3.2.1-0.2.gitf8467404.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing openni-1.3.2.1-0.2.gitf8467404.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-15075
then log in and leave karma (feedback).
Comment 6 Fedora Update System 2011-12-22 20:44:59 EST
openni-primesense-5.0.3.3-1.fc15,openni-1.3.2.1-2.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/openni-primesense-5.0.3.3-1.fc15,openni-1.3.2.1-2.fc15
Comment 7 Fedora Update System 2011-12-22 20:45:32 EST
openni-primesense-5.0.3.3-1.fc16,openni-1.3.2.1-2.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/openni-primesense-5.0.3.3-1.fc16,openni-1.3.2.1-2.fc16
Comment 8 Fedora Update System 2011-12-31 15:25:24 EST
openni-primesense-5.0.3.3-1.fc15, openni-1.3.2.1-2.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 9 Fedora Update System 2011-12-31 15:25:45 EST
openni-primesense-5.0.3.3-1.fc16, openni-1.3.2.1-2.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.

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