On 7/26/07, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
>
> We can go either way. My preference is to keep the "succeeded" to give
> the user just a little more comfort. As a minor side effect, it also
> introduces the user to the -o option of grep.
Sounds good.
--
Dan
--
http://linuxfromscratch.or
Dan Nicholson wrote:
> On 7/26/07, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
>> or just:
>>
>> grep -o '/usr/lib.*/crt[1in].*succeeded' dummy.log
>
> Greg has been using something like this in DIY, but he just checks for
> crt1.o. Also, you could match on the line that follows the "succeeded"
> lin
On 7/26/07, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
>
> or just:
>
> grep -o '/usr/lib.*/crt[1in].*succeeded' dummy.log
Greg has been using something like this in DIY, but he just checks for
crt1.o. Also, you could match on the line that follows the "succeeded"
line that just has the location:
g
Jeremy Huntwork wrote:
> Also, for a while now, the gcc dummy tests have not been totally
> accurate for one section. This command ends up producing a lot more
> output than the book says it will:
>
> grep -o '/usr/lib.*/crt[1in].* .*' dummy.log
>
> Should we refine the above command or the expe
On 7/25/07, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
> Jeremy Huntwork wrote:
> > Heya,
> >
> > Not sure how important this is for the rc books, but chapter 6 gcc tells
> > the user to compare the gcc test results with those at this missing
> > link:
> >
Jeremy Huntwork wrote:
> Heya,
>
> Not sure how important this is for the rc books, but chapter 6 gcc tells
> the user to compare the gcc test results with those at this missing
> link:
>
> http://www.linuxfromscratch.org/lfs/build-logs/6.3-rc1
>
> Just want to m
Heya,
Not sure how important this is for the rc books, but chapter 6 gcc tells
the user to compare the gcc test results with those at this missing
link:
http://www.linuxfromscratch.org/lfs/build-logs/6.3-rc1
Just want to make sure we don't forget to generate these for 6.3.
Also, for a
