From: FX Coudert <fxcoudert@gmail.com>
To: Wayne Davison <wayned@users.sourceforge.net>
Cc: goetz fischer <g.fischer@ah-online.com>, zsh-workers@sunsite.dk
Subject: Re: zsh 4.3.2 bug
Date: Sat, 18 Mar 2006 00:09:02 +0100 [thread overview]
Message-ID: <c17ef800778a593e43f48b8fcec433d6@gmail.com> (raw)
In-Reply-To: <20060317184643.GI24877@dot.blorf.net>
Le 17 mars 06, à 19:46, Wayne Davison a écrit :
> On Fri, Mar 17, 2006 at 06:45:53PM +0100, Fran?ois-Xavier Coudert
> wrote:
>> $ uname -a
>> IRIX64 xxx 6.5 10060437 IP27 mips unknown Irix
>> $ cc -v
>> MIPSpro Compilers: Version 7.4.2m
>
> What are you using for awk? Is is gawk? mawk? nawk? awk?
$ which awk
/usr/bin/awk
$ awk -v
UX:awk: ERROR: No program given
$ awk -help
UX:awk: WARNING: Unknown option -help ignored
UX:awk: ERROR: No program given
$ awk -V
UX:awk: WARNING: Unknown option -V ignored
UX:awk: ERROR: No program given
Doesn't help much :)
> I'm betting
> that the failure that goetz is experiencing is related to this (as I
> mentioned in my prior reply to him on the subject). Another reason may
> well be that your build found a different signal.h header file to
> parse:
> what is the value of SIGNAL_H in your config.log file?
SIGNAL_H='/usr/include/internal/signal_core.h'
configure:11345: result: no
configure:11366: checking what style of signals to use
configure:11397: result: POSIX_SIGNALS
configure:11400: checking where signal.h is located
configure:11439: result: /usr/include/internal/signal_core.h
And I do have:
$ grep -i signal config.h
/* Define to 1 if you use BSD style signal handling (and can block
signals).
/* #undef BSD_SIGNALS */
/* Define to 1 if `ru_nsignals' is member of `struct rusage'. */
#define HAVE_STRUCT_RUSAGE_RU_NSIGNALS 1
/* Define to 1 if you have no signal blocking at all (bummer). */
/* #undef NO_SIGNAL_BLOCKING */
/* Define to 1 if you use POSIX style signal handling. */
#define POSIX_SIGNALS 1
/* Define as the return type of signal handlers (`int' or `void'). */
/* Define to 1 if you use SYS style signal handling (and can block
signals).
/* #undef SYSV_SIGNALS */
/* Define to `unsigned int' if <sys/types.h> or <signal.h> doesn't
define */
FX
next prev parent reply other threads:[~2006-03-17 23:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 10:08 François-Xavier Coudert
2006-03-17 17:18 ` goetz fischer
2006-03-17 17:45 ` François-Xavier Coudert
2006-03-17 18:46 ` Wayne Davison
2006-03-17 23:09 ` FX Coudert [this message]
2006-03-17 23:02 ` goetz fischer
2006-03-19 5:09 ` g.fischer
2006-03-19 21:54 ` Peter Stephenson
-- strict thread matches above, loose matches on Subject: below --
2006-03-12 0:52 g.fischer
2006-03-13 10:42 ` Peter Stephenson
2006-03-14 23:37 ` goetz fischer
2006-03-14 23:56 ` Wayne Davison
2006-03-15 3:07 ` g.fischer
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=c17ef800778a593e43f48b8fcec433d6@gmail.com \
--to=fxcoudert@gmail.com \
--cc=g.fischer@ah-online.com \
--cc=wayned@users.sourceforge.net \
--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).