zsh-users
 help / color / mirror / code / Atom feed
From: "Johann 'Myrkraverk' Oskarsson" <johann@myrkraverk.com>
To: zsh-users@sunsite.dk
Subject: configure: error: ERROR MACROS NOT FOUND:  please report to developers [PATCH]
Date: Sat, 27 May 2006 23:02:19 +0000	[thread overview]
Message-ID: <m3hd3bgjgk.fsf@jin.myrkraverk.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 727 bytes --]

Hi,

Since I'm subscribed to the users mailing list, I'm posting this here.

I've fixed the following configure error on zeta, see:

http://www.yellowtab.com/products/

with the following patch agains 4.2.5.  The RE *may* need or warrant
some further tweakig, but it happens that on Zeta (BeOS) as well as
Haiku, error codes are defined like the following:

#define ESIGPARM                (B_POSIX_ERROR_BASE + 15)

And at least on Haiku, the following can also be seen:

#define ENOMEM             B_NO_MEMORY


Have fun, and I hope you'll incorporate it,


Johann -- working on further tweaks to port zsh

-- 
johann myrkraverk com (you know the drill with the @ and .)
I classify Outlook mail as spam, use something else.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Zeta patch for ZSH --]
[-- Type: text/x-patch, Size: 1387 bytes --]

Common subdirectories: zsh-4.2.5/Completion and zsh-4.2.5-zeta1/Completion
Common subdirectories: zsh-4.2.5/Config and zsh-4.2.5-zeta1/Config
Common subdirectories: zsh-4.2.5/Doc and zsh-4.2.5-zeta1/Doc
Common subdirectories: zsh-4.2.5/Etc and zsh-4.2.5-zeta1/Etc
Common subdirectories: zsh-4.2.5/Functions and zsh-4.2.5-zeta1/Functions
Common subdirectories: zsh-4.2.5/Misc and zsh-4.2.5-zeta1/Misc
Common subdirectories: zsh-4.2.5/Src and zsh-4.2.5-zeta1/Src
Common subdirectories: zsh-4.2.5/StartupFiles and zsh-4.2.5-zeta1/StartupFiles
Common subdirectories: zsh-4.2.5/Test and zsh-4.2.5-zeta1/Test
Common subdirectories: zsh-4.2.5/Util and zsh-4.2.5-zeta1/Util
Common subdirectories: zsh-4.2.5/autom4te.cache and zsh-4.2.5-zeta1/autom4te.cache
diff -uN --exclude-from=zsh-diff-exclude zsh-4.2.5/configure.ac zsh-4.2.5-zeta1/configure.ac
--- zsh-4.2.5/configure.ac	Mon Apr  4 02:48:58 2005
+++ zsh-4.2.5-zeta1/configure.ac	Sat May 27 22:30:41 2006
@@ -1289,7 +1289,7 @@
   dnl Try to make sure it doesn't get confused by files that don't
   dnl have real error definitions in.  Count definitions to make sure.
   nerrs=`test -f $ERRNO_H && \
-  grep '#[ 	]*define[ 	][ 	]*E[0-9A-Z]*[ 	]*[0-9][0-9]*' $ERRNO_H | \
+  grep '#[ 	]*define[ 	][ 	]*E[0-9A-Z]*[ 	]*(*[_A-Z0-9][_A-Z0-9]*' $ERRNO_H | \
   wc -l | sed 's/[ 	]//g'`
   test "x$nerrs" != x && test "$nerrs" -ge 7 && break
 done

             reply	other threads:[~2006-05-27 22:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <johann@myrkraverk.com>
2006-05-27 23:02 ` Johann 'Myrkraverk' Oskarsson [this message]
2006-05-28 19:11   ` Peter Stephenson
2006-05-28 21:05     ` Johann 'Myrkraverk' Oskarsson

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=m3hd3bgjgk.fsf@jin.myrkraverk.com \
    --to=johann@myrkraverk.com \
    --cc=zsh-users@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).