Re: [MiNT] bug in unlink/MiNTLib?

[Andreas Schwab <schwab@suse.de>]

Tomas Berndtsson <tomas@nocrew.org> writes:

|> I've recently compiled fileutils using MiNTLib 0.55.3, and noticed a
|> small problem, which I think is related to MiNTLib, and not
|> fileutils.
|> 
|> The problem is that wrong error code is returned from MiNTLib's
|> unlink() in certain cases.
|> 
|> Assume that the folder /tmp/ exists, but /tmp/test/ does not. Also
|> assume that the file /tmp/foo does not exist. If I then write:
|> 
|> rm /tmp/foo
|> 
|> it will return "ENOENT - No such file or directory", which is
|> correct. However, if I write:
|> 
|> rm /tmp/test/foo
|> 
|> it will return "ENOTDIR - Not a directory"

This is wrong.  It should return ENOENT as well.

Andreas.

-- 
Andreas Schwab                                  "And now for something
SuSE Labs                                        completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg