Bug 465458 - grace built without support for netcdf because of obsolete include path
grace built without support for netcdf because of obsolete include path
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: grace (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: José Matos
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-03 09:04 EDT by Joachim Frieben
Modified: 2008-10-16 11:40 EDT (History)
2 users (show)

See Also:
Fixed In Version: grace-5.1.22-2.fc10
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-10-16 11:40:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Joachim Frieben 2008-10-03 09:04:51 EDT
Description of problem:
Current grace in "rawhide" is now built against netcdf-4 instead of netcdf-3 but include and library paths have not been updated in the spec file.
Therefore, netcdf support is simply disabled during the configure stage.

Version-Release number of selected component (if applicable):
grace-5.1.22-1.fc10

How reproducible:
Always

Steps to Reproduce:
1. Rebuild grace binary packages from the SRPM.
  
Actual results:
netcdf support gets disabled.

Expected results:
netcdf support gets enabled.

Additional info:
After changing build option "--with-extra-incpath=%{_includedir}/netcdf-3" to "--with-extra-incpath=%{_includedir}/netcdf" and dropping (superfluous) option "--with-extra-ldpath=%{_libdir}/netcdf-3", grace builds correctly.
Note: this bug is essentially identical to bug 309941 that I reported a year ago. Please keep an eye on possible library changes when updating the SRPM and/or the build log, thanks!
Comment 1 José Matos 2008-10-16 11:40:03 EDT
It would be nice to have an automatic way to detect this kind of changes. :-)

I mean in this case the difference between the use of shared libraries for different versions of a given package.

The new version has this corrected, thanks for the report.

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