Bug in mkdir from fileutils 4.0 on NEXTSTEP 3.3

[Thomas C Sobczynski]

Hi.  I'd like to report an odd bug I've found in mkdir from fileutils 4.0
under NEXTSTEP 3.3.  It manifests itself when I use "mkdir -p" with a path
that starts with "./".  Here's what I mean:

next> mkdir --verbose -p foo/bar
created directory `foo'mkdir: created directory `foo/bar'
next> rm -r foo
next> mkdir --verbose -p ./foo/bar
mkdir: `.' exists but is not a directory
next> mkdir --version
mkdir (GNU fileutils) 4.0
next> rm -r foo
rm: foo nonexistent
next> mkdir foo
next> rmdir foo
next> mkdir ./foo
next> mkdir ./foo/bar
next> rm -r foo
next> mkdir -p ./foo/bar
mkdir: `.' exists but is not a directory
next> 

If you have any suggestions or comments, I'd appreciate hearing from you.
Thanks in advance.

Tom