#4748: gnutls-3.2.12.1
-------------------------+-----------------------
Reporter: fo | Owner: ken@…
Type: enhancement | Status: assigned
Priority: normal | Milestone: 7.6
Component: BOOK | Version: SVN
Severity: normal | Resolution:
Keywords: |
-------------------------+-----------------------
Comment (by fo):
Normal build, docs installed with
make -C doc/reference install-data-local
Sizes calculated with du -sch ou du -sh. SBU is 180s, and the script just
divide difference in $SECONDS after "cd" into source dir until last
install is done. After that, script does calculations and determines
sizes, but these do not enter in the SBU calculations. Due to the use of
"du -sch", 18M + 85M = 102M is understandable due to roundof effect.
{{{
18M /home/fernando/tmp/paco-build-2014.03.06-11h20m28s/DEST-
gnutls-3.2.12.1
85M /home/fernando/tmp/paco-build-2014.03.06-11h20m28s/gnutls-3.2.12
102M total
5,0M /home/fernando/sshfs/blfs/gnutls-3.2.12.1.tar.xz
5,0M total
a795db68253d1336f1e3c2ee48c1fee4
/home/fernando/sshfs/blfs/gnutls-3.2.12.1.tar.xz
SBU_TIME: .84444444
}}}
Using the same build, perform the tests (some packages do not like "env
LC_ALL=C"):
{{{
cd /home/fernando/tmp/paco-
build-2014.03.06-11h20m28s/gnutls-3.2.12
{ time \
{
env LC_ALL=C make -k check
}
} 2>&1 | tee -a $LOGDIR/$PACKAGE-make-k-check-$DATE.log
}}}
-k is used just for the sake of not having to redo, if some test fail. I
have 5 skips, no *fail in this case.
{{{
real 5m26.458s
user 1m16.056s
sys 0m24.123s
Tests finished, by hand I determine new sizes:
$ du -sch ../*
18M ../DEST-gnutls-3.2.12.1
94M ../gnutls-3.2.12
112M total
Therefore, by hand, determine for the tests
(5⋅60+26,458)/180 = ((5 ⋅ 60) + 26,458) ∕ 180
≈ 1,8136556
SBU_TIME=1.8136556
112-102=10MB is what is added to dir size.
}}}
Now, run complete build, no tests, with switch --enable-gtk-doc, without
make -C doc/reference install-data-local, API docs are then rebuilt and
installed:
{{{
18M /home/fernando/tmp/paco-build-2014.03.06-11h35m32s/DEST-
gnutls-3.2.12.1
88M /home/fernando/tmp/paco-build-2014.03.06-11h35m32s/gnutls-3.2.12
105M total
5,0M /home/fernando/sshfs/blfs/gnutls-3.2.12.1.tar.xz
5,0M total
a795db68253d1336f1e3c2ee48c1fee4
/home/fernando/sshfs/blfs/gnutls-3.2.12.1.tar.xz
SBU_TIME: .97222222
By hand, determine
0,97222222−0,84444444 = 0,97222222 − 0,84444444
= 0,12777778
105−102 = 105 − 102
= 3
Thus
SBU_TIME added for rebuild: 0.12777778
Dis size added for rebuild: 3MB
}}}
With these data, I would add to the book:
{{{
Download MD5 sum: a795db68253d1336f1e3c2ee48c1fee4
Download size: 5,0 MB
Estimated disk space required: 102 MB (additional 10 MB for the tests, 3
MB
if rebuilding the API documentation)
Estimated build time: 0.8 SBU (additional 1.8 SBU for the tests and 0.1
SBU
for API documentation rebuild)
}}}
I am not worried about small differences, because many are the possible
reasons.
But we have two large differences, I would even say discrepancies, it
seems that we are giving the same name for different things:
additional 3MB for API rebuilt is necessary in disk (you could have, say
3.5, 2.8. no problem). But "less 1 MB" means we are talking about
different things.
additional 0.1 SBU for API rebuilt is necessary (almost nothing) but 1.3
SBU that you gave, also clearly seems to me we are talking about different
things.
One thing I do not find important but do not understand is the tarball
size that I have 5,0 MB and you 4.9 MB. Most differences in sizes above
come from you using 64bit and I using 32bit systems. But "du" gives
different values for the same tarball, having the same md5sum, depending
on the architecture?
What can be done in order to not confuse ourselves and the readres?
--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/4748#comment:6>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
--
http://linuxfromscratch.org/mailman/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
