On Wed, 2005-06-15 at 22:57 -0600, Archaic wrote:
On Wed, Jun 15, 2005 at 11:47:47PM -0500, Randy McMurchy wrote:
As a builder, and especially as a BLFS editor, I want to run
these 3 steps individually, and examine the output of each log
file. Sure, this is tedious, but I don't care. If
to be measuring package build times? I expect the SBU
calculations for the BOOK involve the end user measuring binutils in
Chapter 5, then using that as a GUIDE on how long remaining packages will
take, rather than actually caluclating their own as they go.
Certainly the editors\testers need
On 6/17/05, Steve Crosby [EMAIL PROTECTED] wrote:
SBU's are a wild-ass guess. The methodology of calculating SBU's is fine,
but the application of someone else's build time measurements bear only
rough resemblance to my system - specifically because of architecture,
disk, memory, CPU cache
Tushar Teredesai wrote:
On 6/17/05, Steve Crosby [EMAIL PROTECTED] wrote:
SBU's are a wild-ass guess. The methodology of calculating SBU's is fine,
but the application of someone else's build time measurements bear only
rough resemblance to my system - specifically because of architecture,
DJ Lucas wrote:
I'd guestimate that approx 90% or more of users (probably all
developers) use the the first cmmi for binutils as the baseline SBU just
Change it or don't, but justify
the change.
On second thought, don't. The extra commands are to be installed later
and seem to me to be
Randy McMurchy wrote:
I don't think the last two binutils
commands belong in the timing of the SBU, as these two commands
aren't involved in the build process of the *binutils* pass1
chapter 5 package. These two commands are used as part of the
setup for binutils in pass2. To me I see this
very clear in the book.
For instance, after the make install, add a note like:
Note: If you are timing your build of binutils to determine a base time
for SBU calculations, do not include the following two instructions in
the timing measurements.
If other sections of the book have instructions
On Thu, Jun 16, 2005 at 11:28:40AM -0500, Randy McMurchy wrote:
Okay, we really need this sorted.
Randy: SBU changes will throw everything off
Bruce: SBU changes are minor
I was only holding off due to Randy's concern for the timings, but if it
isn't a big deal, I'd rather the book assumes
Archaic wrote these words on 06/16/05 11:59 CST:
Okay, we really need this sorted.
Let's first decide on how the SBUs will be calculated. It seems
I read Matt is in agreement that configure-make-make install to
build and install the Chapter 5 Pass1 binutils should be used to
calculate.
You and
El Jueves, 16 de Junio de 2005 18:59, Archaic escribi:
On Thu, Jun 16, 2005 at 11:28:40AM -0500, Randy McMurchy wrote:
Okay, we really need this sorted.
Randy: SBU changes will throw everything off
Bruce: SBU changes are minor
I was only holding off due to Randy's concern for the timings,
http://bugs.linuxfromscratch.org/show_bug.cgi?id=1509 has a short
discussion that has turned into how to calculate an SBU.
Basically the issue is this; At which commands do we start and stop the
calculation process? It seems that the most readily definable and
maintainable solution is to include
David Jensen wrote these words on 06/15/05 18:08 CST:
actually I think all the values could be grep'd, cut, adjusted with a
ratio and sed'd, all in a for loop.
Anyone up to the script?
Well, there's certainly no rush. This would be for after BLFS-6.1.
And we must wait until we know what
Archaic wrote these words on 06/15/05 23:30 CST:
On Wed, Jun 15, 2005 at 08:20:04PM -0500, Randy McMurchy wrote:
This is of course, going on Matt and Archaic's recommendation that
the SBU factoring doesn't change until after LFS-6.1.
Randy, what is your take on the proposal for post-6.1?
It
On Wed, Jun 15, 2005 at 11:47:47PM -0500, Randy McMurchy wrote:
As a builder, and especially as a BLFS editor, I want to run
these 3 steps individually, and examine the output of each log
file. Sure, this is tedious, but I don't care. If make fails
because I added a dependency that chokes
14 matches
Mail list logo