Side-by-side configuration is incorrect reported as permission denied

Herbert Stocker
Mon Aug 13 12:51:00 GMT 2012

On 13.08.2012 10:47, Corinna Vinschen wrote:
> On Aug 13 10:24, Herbert Stocker wrote:
>> There is no need for the 'no', i'd suggest ELIBBAD.
> Not bad, either.  So we have ELIBACC, ELIBBADD, and ENOPKG as
> suggestions.
I'd vote against ENOPKG. That means: /* Package not installed */
A side-by-side error does not primarily mean that something is not 

>> (And to bring back to memory, i'd also suggest to add EFAIL be added)
> Here's a clear "no".  EFAIL is not a useful error message.  It's not
> even slightly wrong, like EACCES in this case might be, it's entirely
> lacking information.
My suggestion was not to propose EFAIL as an error message for a 
side-by-side error.
Not at all.
i should have made an extra toipic, actually, and if i would consider it 
important enough, i
would make one now.

What i meant was that sometimes i'm writing a program, and when 
searching for an
appropriate error code in errno.h, i don't find one. Then i would prefer 
to resort to some
genereric EFAIL.
Imagine a routine decodes an mp3 stream and fails because the mp3 data 
is corrupt.
What error code would match this? The best i found was:
    #define EBADMSG 77.     /* Trying to read unreadable message */

But i guess the solution would be to stay away from these more 
OS-centric error codes.

Again, i do not have a strong desire on discussing EFAIL, so we can stop 


Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list