Bug 914831 - %configure macro should set FCFLAGS same a FFLAGS
Summary: %configure macro should set FCFLAGS same a FFLAGS
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: redhat-rpm-config
Version: 18
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Panu Matilainen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-22 22:24 UTC by Orion Poplawski
Modified: 2013-05-03 02:45 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-05-03 02:45:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Orion Poplawski 2013-02-22 22:24:15 UTC
Description of problem:

FCFLAGS is an often used alternative to FFLAGS, especially to distinguish between Fortran 77 (FFLAGS) and Fortran 90+ (FCFLAGS).

Version-Release number of selected component (if applicable):
redhat-rpm-config-9.1.0-37.fc18.noarch

Comment 1 Panu Matilainen 2013-04-23 04:41:43 UTC
Added in rawhide now (redhat-rpm-config-9.1.0-43.fc20)

Comment 2 Fedora Update System 2013-04-24 13:25:58 UTC
redhat-rpm-config-9.1.0-43.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/redhat-rpm-config-9.1.0-43.fc19

Comment 3 Fedora Update System 2013-04-24 16:36:40 UTC
Package redhat-rpm-config-9.1.0-43.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing redhat-rpm-config-9.1.0-43.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-6496/redhat-rpm-config-9.1.0-43.fc19
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2013-05-03 02:45:40 UTC
redhat-rpm-config-9.1.0-43.fc19 has been pushed to the Fedora 19 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.