Opened 20 years ago

Closed 19 years ago

#1574 closed defect (invalid)

How to meassure SBUs on Cross-LFS

Reported by: manuel@… Owned by: lfs-book@…
Priority: highest Milestone:
Component: Book Version: Branch_Cross-LFS
Severity: major Keywords:
Cc:

Description

Due that in the new cross-lfs books is possible to build the temp tools on a different machine than the final system, we can't use any more the first package builded in the book as SBU unit (the Cross Binutils at "Constructing Cross-Compile Tools". Well, actually the first in cross-lfs is Linux-Libc-Headers). Then, I see this roads: .- To remove SBUs. I don't agree but is a possibility. .- To use two SBUs: one for temp tools, based on Cross Binutils, and another for final system, based on ???? (see below). .- To remove SBUs for temp tools. Measure SBUs only for final system packages based on the build time for the first package builded after the reboot/chroot step. That is my preferred way. That package is Tcl installed in /tools. Currently in LFS-SVN the SBU for Tcl is 0.9. In BLFS-SVN is 0.28 + 0.73 for the test suite. Thus making mandatory to run the test suite on Tcl we can have a SBU unit very similar (if not identical) to the current one.

Change History (2)

comment:1 by Matthew Burgess, 19 years ago

Hmm, why doesn't "Cross-LFS" show up in the "Product" drop-down box on this page? I want to move this bug to its proper place and bugzilla apparently won't let me! Anyway, if this is still an issue, can one of the Cross LFS guys create a new bug under the "Cross-LFS" product and close this as INVALID please?

comment:2 by manuel@…, 19 years ago

Resolution: invalid
Status: newclosed

Closed as INVALID. Now that CLFS is a separate project, the policies about SBUs and disk usage should be discusses a defined for CLFS in their own mailing list and bugzilla.

Note: See TracTickets for help on using tickets.