Tony Sequeira wrote:
On Fri, 2006-09-22 at 19:49 +0200, Brandon Peirce wrote:
> Christopher Parker wrote:
>
> >The source of this problem was due to GAWK not parsing the parameters
> >correctly. I now have the problem that the following command
> >
> >echo "parm1 parm2" | awk '{print $1}'
> >
>
On Fri, 2006-09-22 at 19:49 +0200, Brandon Peirce wrote:
> Christopher Parker wrote:
>
> >The source of this problem was due to GAWK not parsing the parameters
> >correctly. I now have the problem that the following command
> >
> >echo "parm1 parm2" | awk '{print $1}'
> >
> >resolves to "parm1 p
Christopher Parker wrote:
The source of this problem was due to GAWK not parsing the parameters
correctly. I now have the problem that the following command
echo "parm1 parm2" | awk '{print $1}'
resolves to "parm1 parm2" instead of just "parm1". Has anyone seen this
before, or have any sug
- Original Message -
From: "Christopher Parker" <[EMAIL PROTECTED]>
To: "LFS Support List"
Sent: Sunday, September 10, 2006 9:39 PM
Subject: Re: ncurses build problem
It's taken me a while to get back to this. Here is the info. awk is at
version 3.1.4.
The error messages I see a
