From: Richard Coleman <coleman@math.gatech.edu>
To: Scott Lipcon <slipcon@insux4.cs.jhu.edu>
Cc: zsh-workers@math.gatech.edu
Subject: Re: Solaris x86?
Date: Tue, 29 Oct 1996 08:12:58 -0500 [thread overview]
Message-ID: <199610291312.IAA10859@redwood.skiles.gatech.edu> (raw)
In-Reply-To: Your message of "Fri, 25 Oct 1996 20:38:59 EDT." <Pine.SOL.3.91.961025203624.18222A-100000@insux4.cs.jhu.edu>
>
> Hi... I think I figured out the problem, but I can't solve it! In the
> FAQ, there is a mention that nawk on some systems has a bug which causes
> the signal handling to be treated wrong. The workaround is to use gawk.
> That is why it compiled fine on the sparc solaris 2.5 machine but not any
> of the pentium solaris 2.5 machines. the sparc has gawk installed. I
> tried to compile gawk, and it wont compile on the pentiums either! So, I
> figured no big deal - I'll just use gawk on the sparc to generate the
> correct signames.h file for the pentium, but I can't for the life of me
> figure out how to do that.
>
> You might want to add this to the Machines file if you can reproduce it -
> Solaris 2.5's nawk doesn't work right.
The nawk on Solaris x86 should work fine (as it is from the same code
code as the one on Solaris sparc). I suspect you are trying to use
a gcc that hasn't been installed correctly. Did you run the script to
fix the includes when you installed gcc?
rc
next prev parent reply other threads:[~1996-10-29 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-25 15:14 Scott Lipcon
1996-10-25 15:31 ` Zefram
1996-10-25 15:35 ` Scott Lipcon
1996-10-25 15:42 ` Hrvoje Niksic
1996-10-25 15:48 ` Scott Lipcon
1996-10-25 15:59 ` Hrvoje Niksic
1996-10-26 0:38 ` Scott Lipcon
1996-10-29 13:12 ` Richard Coleman [this message]
1996-10-29 13:39 ` Scott Lipcon
1996-11-06 18:55 ` Scott Lipcon
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=199610291312.IAA10859@redwood.skiles.gatech.edu \
--to=coleman@math.gatech.edu \
--cc=slipcon@insux4.cs.jhu.edu \
--cc=zsh-workers@math.gatech.edu \
/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).