Re: truncate-fail-diag failure on Solaris

[Jim Meyering]

Bruno Haible <address@hidden> wrote:
> Pádraig Brady wrote:
>> Solaris 10 gives an ENOTDIR error, while linux gives an EISDIR error.
>> I'm not sure what to do in this case. Probably just remove the second
>> truncate test in that file altogether.
>
> The test is useful. You could see whether the file name ends in '/' before
> you call open() on it, no?

To work around such broken systems without polluting
all application code, in the past we've used wrapper
functions like the ones around stat, lstat and rename.
They would be enabled (with overhead) only if a configure-time
test detects the broken syscall.  We could probably do the
same with open to accommodate solaris 7, but I don't think
it's worth the effort for a system that old:

I'd prefer to simply skip the test on losing systems, e.g.,

    case $host_triplet in
      ...) skip_test_ 'open does not work as expected';;
    esac

The only Solaris systems I have access to match *-solaris2.10.
If someone can fill in the "..." blank, I'll add the above.