Re: lfs build-logs
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.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: lfs build-logs
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 line that just has the location: grep '^/usr/lib.*/crt[1in].o' dummy.log I didn't check that on a bootstrapped build, so I'm not sure it would list the same way when using /tools/bin/gcc. Either of these should be good. Is that what we really want or is it important (or just nice) to have the succeeded part in the output? 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. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: lfs build-logs
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 expectd output?
I'm trying to figure out how to modify the pattern. We are getting:
/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/collect2 --eh-frame-hdr -m elf_i386
-dynamic-linker /lib/ld-linux.so.2
/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/../../../crt1.o
/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/../../../crti.o
/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/crtbegin.o
-L/usr/lib/gcc/i686-pc-linux-gnu/4.1.2
-L/usr/lib/gcc/i686-pc-linux-gnu/4.1.2
-L/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/../../.. /tmp/ccsdiSZO.o
--verbose -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed
-lgcc_s --no-as-needed /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/crtend.o
/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/../../../crtn.o
(One line, wrapped)
in addition to our desired output.
How about:
grep -o -E '/usr/lib.*/crt[1in].* .{5,20}$' dummy.log
or just:
grep -o '/usr/lib.*/crt[1in].*succeeded' dummy.log
even shorter, but more obscure:
grep -o '/usr/lib.*/crt[1in].*d$' dummy.log
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Re: lfs build-logs
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 make sure we don't forget to generate these for 6.3. I don't have a copy of my logs, but I put in a stub for the logs. Dan, can you add the logs for -rc1? 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 expectd output? I remember that discussion. I thought we fixed it. I'll check into it some more. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: lfs build-logs
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: 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. I don't have a copy of my logs, but I put in a stub for the logs. Dan, can you add the logs for -rc1? I don't have them at the moment, and I'm not at my main build box. Manuel is probably the best candidate since he can whip together a jhalfs build rather quickly. He may even have logs from the other day when he did a test build. 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 expectd output? I remember that discussion. I thought we fixed it. I'll check into it some more. I recall that, but nothing ever came of it. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
