From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Lecessi, Ralph" <ralph(dot)lecessi(at)lmco(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Bug #669: gawk: cmd. line:2: (END OF FILE) |
Date: | 2002-05-21 16:57:01 |
Message-ID: | 21575.1022000221@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"Lecessi, Ralph" <ralph(dot)lecessi(at)lmco(dot)com> writes:
>>Do you have another flavor of awk available to try? I still doubt that
>>it's gawk's fault, but we need to eliminate possibilities.
> I ran with nawk (/usr/bin/nawk) & the parse error went away.
Interesting. What version of gawk have you got? People build all the
time using gawk on Linux, and no one's ever reported such a failure that
I can recall. (FWIW, "gawk --version" reports 3.1.0 on my Linux box,
and I also build successfully with gawk 3.0.4 on my HPUX box.)
> Is their any way I can check if the awk output is valid (is their
> anything I can check for or compare with) ?
If you can initdb and run the regression tests successfully, then you
can be quite certain genbki worked.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Lecessi, Ralph | 2002-05-21 17:30:27 | Re: Bug #669: gawk: cmd. line:2: (END OF FILE) |
Previous Message | Lecessi, Ralph | 2002-05-21 16:28:54 | Re: Bug #669: gawk: cmd. line:2: (END OF FILE) |