On Tue, Feb 13, 2001 at 05:36:39PM +1000, Allan Rae wrote:
> On Tue, 13 Feb 2001 [EMAIL PROTECTED] wrote:
> > 1. Don't assume the system grep understands -E. Use egrep instead.
>
> Agreed. But do we really need egrep or is grep sufficient?
I don't think grep works with '|'.
> > 2. Search for nawk-equivalent (awk cannot handle syntax in
> > po/Makefile.in.in)
>
> Your patch is not against latest CVS. The first chunk of
> po/Makefile.in.in has been rewritten already to only use sed (no awk or
> grep).
>
> The second one has also changed slightly.
>
> I guess you have used 1.1.6fix? as your base? My patches to
> po/Makefile.in.in haven't been applied to that tree yet. Since noone has
> complained about them yet they should be safe to introduce, JMarc.
Oh yes, I'm using 1.1.6fix as the base. Sorry.
> > - awk -F '"' '$$2 {printf "_(\"%s\");\n", $$2}' $(top_srcdir)/lib/languages >> $@
> > + $(NAWK) -F '"' '$$2 {printf "_(\"%s\");\n", $$2}' $(top_srcdir)/lib/languages
>>> $@
>
> What doesn't awk handle that nawk does?
It doesn't like the $$2 in the beginning:
$ awk '$0 {print $0}' /etc/passwd
awk: syntax error near line 1
awk: bailing out near line 1
> > - awk 'BEGIN {FS= ":"} {print $$1}' | \
> > + $(NAWK) 'BEGIN {FS= ":"} {print $$1}' | \
>
> And here?
This works fine. I thought I'd replace every awk with $(NAWK), even
where not needed for consistency.
--
albert chin ([EMAIL PROTECTED])
