zsh-workers
 help / color / mirror / code / Atom feed
From: Dan Nelson <dnelson@allantgroup.com>
To: "arno." <arno.@no-log.org>
Cc: zsh-workers@sunsite.dk
Subject: Re: bug in zsh/system : `syserror ENOENT` doesn't work
Date: Fri, 8 Sep 2006 12:53:20 -0500	[thread overview]
Message-ID: <20060908175320.GC30620@dan.emsphone.com> (raw)
In-Reply-To: <20060908170142.GA32049@localhost.localdomain>

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@allantgroup.com


  reply	other threads:[~2006-09-08 17:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-08 17:01 arno.
2006-09-08 17:53 ` Dan Nelson [this message]
2006-09-08 21:50   ` Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060908175320.GC30620@dan.emsphone.com \
    --to=dnelson@allantgroup.com \
    --cc="arno."@no-log.org \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).