Bug 246450 - dangling symlinks
Summary: dangling symlinks
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: openmpi   
(Show other bugs)
Version: rawhide
Hardware: All Linux
low
low
Target Milestone: ---
Assignee: Doug Ledford
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-07-02 10:34 UTC by Florian La Roche
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-07-02 14:19:59 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Florian La Roche 2007-07-02 10:34:45 UTC
Description of problem:

openmpi-devel has dangling symlink from /usr/share/openmpi/1.2.3-gcc/bin32/mpiCC
to /usr/bin/opal_wrapper-1.2.3-%{cc}-32
openmpi-devel has dangling symlink from
/usr/share/openmpi/1.2.3-gcc/bin32/mpic++ to /usr/bin/opal_wrapper-1.2.3-%{cc}-32
openmpi-devel has dangling symlink from /usr/share/openmpi/1.2.3-gcc/bin32/mpicc
to /usr/bin/opal_wrapper-1.2.3-%{cc}-32
openmpi-devel has dangling symlink from
/usr/share/openmpi/1.2.3-gcc/bin32/mpicxx to /usr/bin/opal_wrapper-1.2.3-%{cc}-32
openmpi-devel has dangling symlink from
/usr/share/openmpi/1.2.3-gcc/bin32/mpif77 to /usr/bin/opal_wrapper-1.2.3-%{cc}-32
openmpi-devel has dangling symlink from
/usr/share/openmpi/1.2.3-gcc/bin32/mpif90 to /usr/bin/opal_wrapper-1.2.3-%{cc}-32

The spec file also uses opt_cc as macro, maybe that is needed instead of
the %{cc} one?

regards,

Florian La Roche




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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Doug Ledford 2007-07-02 14:19:59 UTC
Oops, you're right.  Building 1.2.3-2 right now to resolve this issue.


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