This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 485697 - build ignores optflags
build ignores optflags
Product: Fedora
Classification: Fedora
Component: jhead (Show other bugs)
All All
low Severity low
: ---
: ---
Assigned To: Adrian Reber
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-02-16 08:53 EST by Moritz Barsnick
Modified: 2009-03-05 11:32 EST (History)
1 user (show)

See Also:
Fixed In Version: 2.86-1.fc9
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-03-05 11:31:53 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Moritz Barsnick 2009-02-16 08:53:00 EST
Description of problem:
The build process given in jhead's SPEC file does not correctly pass the optflags to make.

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

How reproducible:

Steps to Reproduce:
1. rpmbuild -ba SPECS/jhead.spec
Actual results:
Don't see the common optflags being set.

Expected results:
Observe the common optflags being set.

Additional info:
This is the current make call:
CFLAGS="$RPM_OPT_FLAGS" make %{?_smp_mflags}

It passes the CFLAGS as an environment variable, not as a make variable.

This call is correct and works (tested by myself):
make %{?_smp_mflags} CFLAGS="$RPM_OPT_FLAGS"

BTW, 2.86 is available. :-)
Comment 1 Adrian Reber 2009-02-16 09:24:35 EST
Thanks. I will include your fix. Thanks for letting me know about 2.86.
Comment 2 Fedora Update System 2009-03-05 11:31:48 EST
jhead-2.86-1.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 3 Fedora Update System 2009-03-05 11:32:43 EST
jhead-2.86-1.fc9 has been pushed to the Fedora 9 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.