[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/971] New: ranlib: unable to copy file 'XX' reason: Permiss

From: woodd at deshaw dot com
Subject: [Bug binutils/971] New: ranlib: unable to copy file 'XX' reason: Permission denied
Date: 25 May 2005 20:58:40 -0000

This problem started in v2.15 and it still exists in v2.16 and HEAD.  It occurs
on Linux, Solaris, and probably others.  Previously, ranlib would only complain
about library write permission if a new index needed to be written.

  lx-r64.nyc:/tmp > ls -al libz.a
  -r-xr-x--x  1 woodd wheel 71704 May 25 16:46 libz.a
  lx-r64.nyc:/tmp > /usr/local/gnu/bin/ranlib --version | head -1
  GNU ranlib 2.13
  lx-r64.nyc:/tmp > /usr/local/gnu/bin/ranlib libz.a
  lx-r64.nyc:/tmp >

  lx-r64.nyc:/tmp > /usr/bin/ranlib --version | head -1
  GNU ranlib 20040927
  lx-r64.nyc:/tmp > /usr/bin/ranlib libz.a
  /usr/bin/ranlib: unable to copy file 'libz.a' reason: Permission denied
  lx-r64.nyc:/tmp > chmod +w libz.a
  lx-r64.nyc:/tmp > /usr/bin/ranlib libz.a
  lx-r64.nyc:/tmp > 

You would expect a permission error only if you actually needed to write to the
file.  This how Sun (and probably others) behave:

  bsqa1.nyc:/tmp > ls -al foo.a
  -r--r-----   1 woodd    staff     382570 May 24 14:55 foo.a
  bsqa1.nyc:/tmp > /usr/ccs/bin/ar -t foo.a > /dev/null
  bsqa1.nyc:/tmp > /usr/ccs/bin/ar -ts foo.a > /dev/null
  ar: cannot write foo.a
          Permission denied

I believe the bug was introduced in revision 1.8 of binutils/rename.c:


Thank you for your time.  David

           Summary: ranlib: unable to copy file 'XX' reason: Permission
           Product: binutils
           Version: 2.15
            Status: NEW
          Severity: normal
          Priority: P2
         Component: binutils
        AssignedTo: unassigned at sources dot redhat dot com
        ReportedBy: woodd at deshaw dot com
                CC: bug-binutils at gnu dot org


------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]