Trailing slashes on file names

[Christian Weisgerber]

I'm trying to figure out why ports/archivers/gcpio is reported as
not building on sparc64.  The details seem to be twisty, but I
suspect at the root are these different results of a number of
configure script tests:

==== sparc64 ====
checking whether chown honors trailing slash... no
checking whether lstat dereferences a symlink specified with a trailing slash... no
checking whether unlink honors trailing slashes... no
checking whether open recognizes a trailing slash... no
checking whether stat handles trailing slashes on files... no
checking whether unlink honors trailing slashes... (cached) no

==== amd64, i386 ====
checking whether chown honors trailing slash... yes
checking whether lstat dereferences a symlink specified with a trailing slash... yes
checking whether unlink honors trailing slashes... yes
checking whether open recognizes a trailing slash... yes
checking whether stat handles trailing slashes on files... yes
checking whether unlink honors trailing slashes... (cached) yes

Whatever the expected behavior, it certainly shouldn't vary with
the architecture.  Is this a problem of FreeBSD/sparc64?  Something
in the build environment for the sparc64 section of the pointyhat
cluster?

-- 
Christian "naddy" Weisgerber                          naddy at mips.inka.de