Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: bug in zsh/system : `syserror ENOENT` doesn't work
- X-seq: zsh-workers 22680
- From: Dan Nelson <dnelson@xxxxxxxxxxxxxxx>
- To: "arno." <arno.@xxxxxxxxxx>
- Subject: Re: bug in zsh/system : `syserror ENOENT` doesn't work
- Date: Fri, 8 Sep 2006 12:53:20 -0500
- Cc: zsh-workers@xxxxxxxxxx
- In-reply-to: <20060908170142.GA32049@xxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20060908170142.GA32049@xxxxxxxxxxxxxxxxxxxxx>
In the last episode (Sep 08), arno. said:
> In module, zsh/system, some symbolic names are not recognized, but are
> recognized otherwise by my system (Debian testing)
>
> ? zmodload zsh/system
> ? syserror ENOENT
> ? echo $?
> 2
>
> So, I have to refer to them with their number
>
> ? syserror E2
> No such file or directory
> ? syserror 2
> No such file or directory
>
> errnos are defined on my system in /usr/include/asm-generic/errno.h
> and that file contains the line :
> #include <asm-generic/errno-base.h>
Actually errnos are defined in /usr/include/errno.h . Linux happens to
#include a maze of twisty headers, each defining some errors along the
way. The zsh configure script looks like it starts at errno.h and
tries find the included header with the most defines in it. Maybe it
should just build a list of candidate files and pass them all to
errnames1.
--
Dan Nelson
dnelson@xxxxxxxxxxxxxxx
Messages sorted by:
Reverse Date,
Date,
Thread,
Author