X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
X-Authentication-Warning: itservs.wilkes.edu: apache set sender to fdonahoe AT wilkes DOT edu using -f
Message-ID: <1107876721.4208db71134a7@webmail.wilkes.edu>
Date: Tue,  8 Feb 2005 10:32:01 -0500
From: fdonahoe AT wilkes DOT edu
To: djgpp-workers AT delorie DOT com
Subject: filutils 4.1 and the new symlink
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2
X-Originating-IP: 146.94.1.216
Reply-To: djgpp-workers AT delorie DOT com

Fhe source from package fil41s.zip release 7, previously installed
were recompiled with gcc 3.4.3 and the rebuilt DJGPP 2.04 on 
Windows XP Home Edition.  There was only one warning:

    ln.c:229: warning: the address of `symlink', will always \
              evaluate as `true'

229:  && (backup_type == none || !symlink)

Here is a summary of 'tests.summ' showing the results for those
tests which were expected to fail with djgpp 2.03 because of
the absents of symlinks in that version.  Won some, lost some.
Pity I forgot to preserve the results for the build with gcc 3.4.2
and the old `symlink.c'.  The scripts are unforgiving.

chgrp  failed:  recurse
       skipped:  deref

cp     passed:  nderfil1, nderfil2, nderfil3, symlink-slash,
               link, deref-slink
       failed:  same-file, slink-2-slink, cp-HL

ln     passed:  sf-1, misc

ls     passed:  symlink-slash
       failed:  no-arg

mv     passed:  to-self4
       failed:  part-symlink

touch  failed: dangling-symlink

touch  also failed `empty-file' which versions compiled with
       djgpp203 were expected to pass.

`ln' performs as expected.  If `bar.exe' be in the current directory
"ln -s bar.exe foo.exe" produces a 2K stub and when `foo' is called
`bar' executes.

"ln -s src/bar.exe foo" produces a 510 byte symlink which will not
execute `bar' even under bash, but, for example, "strings foo" will
report the strings in `bar.exe'.

Frank



-----------------------------------------------------------------------
This mail was sent through Wilkes Webmail: http://webmail.wilkes.edu
Wilkes Webmail is using IMP: http://horde.org/imp/