M.Canales.es wrote these words on 04/24/06 14:40 CST:
> Disk usage is made in to steeps, a first "du -skx $LFS" before to unpack the
> package, and a second "du -skx $LFS" before to delete the sources and build
> dirs (excluding in both cases the jhalfs dir to not measure build log files).
Sounds right.
> Build time is measured enclosing each script run inside time {} commands. The
> time used to unpack the tarball, to remove the sources and build dirs, and to
> run both du commands aren't measured.
Good so far.
> But the time needed to apply patches,
What time is this. The 100th of a millisecond? :-)
> unpack additional packages (like libidn, bash-doc or vim-languages)
To me, this skews things badly. We've never ever counted unpacking
source tarballs before.
> or other
> extra commands placed inside the book instructions (like creating
> configuration files) are measured.
Something else that has *always* been *deliberately* left out. Of
course in an automated build, it doesn't matter as we're back to
the 100th of a millisecond. :-)
> That should to work. But comparing the values obtained from my last jhalfs
> build with the current ones in the book, the differences are abismal in some
> cases. For example, for GCC-pass1 in the book we have:
Yes, many are grossly wrong.
--
Randy
rmlscsi: [bogomips 1003.28] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3]
[GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686]
15:04:00 up 30 days, 2:41, 1 user, load average: 0.79, 0.35, 0.14
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
