From: Yngve Svendsen <yngve.svendsen@sun.com>
To: Paul Richardson <prichardson@tricn.com>
Cc: help-gnats@gnu.org
Subject: Re: diff-prs
Date: Mon, 22 Sep 2003 18:04:00 -0000 [thread overview]
Message-ID: <3F6CDC21.9020007@sun.com> (raw)
In-Reply-To: <A3430B452D2C4B448141750D9585A1BF03BA1F@tcnexchange.tricn.com>
Paul Richardson wrote:
> Before I embark on learning some awk, I was wondering if anyone else in
> the 4.0 release of gnats. I get errors pointing to lines 24 -> 26 of
> diff-prs when I try and run it on our solaris system. What happens is
> when I invoke edit-pr and get to the point where I change the value of
> the state and then write the modified pr out, I get a dialogue
> indicating that I should give a reason for the change. The problem seems
> to be I the awk code in diff-prs…
I just committed a fix to CVS. Basically, /usr/bin/awk on Solaris is
ancient, so it doesn't support the sub command for substring
substitution, which is what happens on lines 24, 25 and 26 in the
diff-prs script. Solaris and other OSes with old awks usually have a
'nawk' command which is a more modern awk implementation.
I have added the standard autoconf check for awk to the GNATS configure
setup. This basically checks for gawk, mawk, nawk, and awk, in that
order (gawk, GNU awk, is generally considered the best implementation),
and uses the best implementation available in the diff-prs script.
Look at https://savannah.gnu.org/cvs/?group=gnats for instructions on
checking out the CVS version of GNATS.
Yngve Svendsen
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
prev parent reply other threads:[~2003-09-20 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-20 9:46 diff-prs Paul Richardson
2003-09-20 23:03 ` diff-prs Yngve Svendsen
2003-09-22 18:04 ` Yngve Svendsen [this message]
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=3F6CDC21.9020007@sun.com \
--to=yngve.svendsen@sun.com \
--cc=help-gnats@gnu.org \
--cc=prichardson@tricn.com \
/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).