From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-users@sunsite.dk, pws@pwslaptop.csr.com
Subject: Re: configure: error: ERROR MACROS NOT FOUND: please report to developers [PATCH]
Date: Sun, 28 May 2006 20:11:56 +0100 [thread overview]
Message-ID: <200605281911.k4SJBuAF004114@pwslaptop.csr.com> (raw)
In-Reply-To: Message from "Johann 'Myrkraverk' Oskarsson" <johann@myrkraverk.com> of "Sat, 27 May 2006 23:02:19 -0000." <m3hd3bgjgk.fsf@jin.myrkraverk.com>
"Johann 'Myrkraverk' Oskarsson" wrote:
> 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
>...
> '#[ ]*define[ ][ ]*E[0-9A-Z]*[ ]*(*[_A-Z0-9][_A-Z0-9]*'
[line stripped to patternt to fit without wrapping.
The current code (4.3) uses an egrep pattern,
'#[ ]*define[ ][ ]*E[0-9A-Z]*[ ]*(_HURD_ERRNO \()?[0-9]+\)?'
so it looks like yours isn't good enough any more. Also, since there's
no $ anchor (difficult in general since there may be comments at the end
of the line) the last [_A-Z0-9]* doesn't have any effect on the match,
and it's not clear turning the * into a + would make much difference.
The following covers both cases, but may be too general:
'#[ ]*define[ ][ ]*E[0-9A-Z]*[ ]*(_HURD_ERRNO )?\(?[_A-Z0-9]'
Any further tweaks (from any system)?
--
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/
next prev parent reply other threads:[~2006-05-28 19:12 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
2006-05-28 19:11 ` Peter Stephenson [this message]
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=200605281911.k4SJBuAF004114@pwslaptop.csr.com \
--to=p.w.stephenson@ntlworld.com \
--cc=pws@pwslaptop.csr.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).