bug-findutils
[Top][All Lists]
Advanced

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

[bug #19973] Setup for samefile-p-brokenlink.exp fails


From: James Youngman
Subject: [bug #19973] Setup for samefile-p-brokenlink.exp fails
Date: Sat, 26 May 2007 13:02:49 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060830 Firefox/1.5.0.7 (Debian-1.5.dfsg+1.5.0.7-2)

URL:
  <http://savannah.gnu.org/bugs/?19973>

                 Summary: Setup for samefile-p-brokenlink.exp fails
                 Project: findutils
            Submitted by: jay
            Submitted on: Saturday 05/26/2007 at 13:02
                Category: find
                Severity: 2 - Minor
              Item Group: None
                  Status: Need Info
                 Privacy: Public
             Assigned to: jay
         Originator Name: Nelson H. F. Beebe
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.3.6
           Fixed Release: None

    _______________________________________________________

Details:

When the test setup phase of 
find/testsuite/find.gnu/samefile-p-brokenlink.exp is carried out on OpenBSD
3.9 and on Solaris 10, it fails:

Running
/local/build/bare/findutils-4.3.6/find/testsuite/find.gnu/samefile-same.exp
...
ERROR: tcl error sourcing
/local/build/bare/findutils-4.3.6/find/testsuite/find.gnu/samefile-p-brokenlink.exp.
ERROR: ln: accessing `tmp/broken': No such file or directory
    while executing
"exec ln    tmp/broken tmp/blink"
    (file
"/local/build/bare/findutils-4.3.6/find/testsuite/find.gnu/samefile-p-brokenlink.exp"
line 8)
    invoked from within
"source
/local/build/bare/findutils-4.3.6/find/testsuite/find.gnu/samefile-p-brokenlink.exp"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 source
/local/build/bare/findutils-4.3.6/find/testsuite/find.gnu/samefile-p-brokenlink.exp"
    invoked from within
"catch "uplevel #0 source $test_file_name""



I am not sure yet what causes this, but I suspect that on this system it is
not possible to create a hard link to a broken symlink, or perhaps it is
possible but it requires the use of an option that we are not using.    

A useful diagnostic would be to attempt these two similar but different shell
commands on the two systems under consideration:-

# 1
rm -rf broken link; 
ln -s nosuchfile broken; 
ln -n broken link; 
ls -il broken link

# 2
rm -rf broken link; 
ln -s nosuchfile broken; 
ln   broken link; 
ls -il broken link

#1 corresponds to what we do now, and #2 passes an -n flag to ln.





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?19973>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/





reply via email to

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