Bug 595429 - libtool must not rely on hard links
Summary: libtool must not rely on hard links
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: libtool
Version: 5.7
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: 5.9
Assignee: Pavel Raiskup
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks: 918449
TreeView+ depends on / blocked
 
Reported: 2010-05-24 15:28 UTC by Murilo Opsfelder Araujo
Modified: 2018-11-30 22:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 918449 (view as bug list)
Environment:
Last Closed: 2013-03-07 10:53:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Murilo Opsfelder Araujo 2010-05-24 15:28:59 UTC
Description of problem:
The file /usr/share/libtool/ltmain.sh provided by libtool package uses hard links to lock single object files with the generated libtool script and causes error on file systems that don't support or allow hard links (e.g.: AFS).

Version-Release number of selected component (if applicable):
% rpm -qa libtool 
libtool-1.5.22-7.el5_4

How reproducible:
Always.

Steps to Reproduce:
1. Build a program that uses libtoolize on a file system that doesn't support or allow hard links.
2.
3.

Actual results:
/usr/share/libtool/ltmain.sh tries to create hard links.

Expected results:
/usr/share/libtool/ltmain.sh should create soft links.

Additional info:

Comment 6 Pavel Raiskup 2013-03-07 10:53:18 UTC
Hi Murilo, Nathan,

I'm very sorry but it is probably too late to address this issue in RHEL5.  We
are currently in Production phase 2 [1], it means that only security and
critical issues are going to be fixed.

In addition to that, this bugzilla is about upstream issue discussed about
10 years back by upstream and no fix was provided yet.  It is quite unlikely
that this will ever be fixed in RHEL5 thus I'm closing this bugreport as
WONTFIX.  Note that I have created clone bug (#918449) for Fedora rawhide just
to properly track upstream issue (CCing everybody here).  Another possibility
worth to try would be to clone this issue against next major release RHEL6.

Thanks for your report,
Pavel

[1] https://access.redhat.com/support/policy/updates/errata/


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