From: doug.mildram@mindspeed.com
To: help-gnats@gnu.org
Subject: solaris "nawk" fixes edit-pr awk: syntax error
Date: Thu, 14 Mar 2002 10:54:00 -0000 [thread overview]
Message-ID: <200203141851.g2EIpSt09542@dogbert.westboro.mindspeed.com> (raw)
Running edit-pr under solaris in some instances,
e.g. changing State: or another reason-required field,
causes edit-pr to attempt to prompt you for a reason,
but under solaris, instead it barfs out:
awk: syntax error near line 24
awk: illegal statement near line 24
I recalled that there was a "nawk", newer than "awk", and Solaris
keeps them both in /bin, foolishly? choosing not to make "nawk"
the default "awk". I found that edit-pr was really calling
$LIBEXECDIR/gnats/diff-prs
....which is a "sh" script that really just does "awk",
and lucky me, nawk seems to silence the lambs,
and may even stop edit-pr from getting into a sick loop where it
offers you to "(a)bort or (r)etry? " ,
but (due to awk error) (r)etry silently bombs out,
so edit-pr keeps saying "(a)bort or (r)etry? "
until you (a)bort....
at which point it claims that
"Changed pr is in /tmp/epNNNN" (NNNN==PID),
but...............the "trap" in edit-pr has REMOVED $new.
MINOR suggestion: no harm in littering /tmp with epNNNN files.
around line 120 in edit-pr I'm changing
#trap 'rm -f $new $new.old $change_msg $fixfil ; exit 0' 0
changing to
trap 'rm -f $new.old $change_msg $fixfil ; exit 0' 0
MAJOR FIX: for solaris diff-prs ....change awk to nawk.
25c25
< awk '
---
> nawk '
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next reply other threads:[~2002-03-14 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 10:54 doug.mildram [this message]
2002-05-20 5:28 ` Milan Zamazal
2002-05-20 11:42 ` Mel Hatzis
2002-05-26 8:37 ` Milan Zamazal
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=200203141851.g2EIpSt09542@dogbert.westboro.mindspeed.com \
--to=doug.mildram@mindspeed.com \
--cc=help-gnats@gnu.org \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).