Hi,
Mike N wrote:
it's a nice idea to implement something like this, but I guess getting
As a quick conceptual test you could start not worrying about the
real error, but build any failed package a second time without
TMPFS, this might be just a couple of lines of code.
I have now made some tweaks in Build-Target script. Modified pkgloop_action
function as follows
- If SDECFG_SRC_TMPFS = 1 and compilation failed then temporarly remove that
TMPFS option and try to re-run the same cmdbuild_pkg command again. After
this extra attempt TMPFS option is restored back to original value.
I just did "full rebuild of generic minimal-desktop" configuration and
target WITHOUT that option. However, after compiling it I realized that it
had downloaded number of new packages, so total compilation time is not
actually comparable.
T2 web page lists average compilation times per package. Can I see the same
information locally from some log file? This way I could try to compare
actual compiler times per package with and without this "tmpfs re-try
modification".
The buildtime listed on the website is the build time relative
to the binutils package build (kind of inspired from Linux From
Scratch - LFS) to have a compariable "standard" meassurement.
The relative indicator should also compare to some degree
between different hardware.
You can find the value in the package's .cache file, the ones
om the homepage are generated from the T2 SVN sources, and
your fresh build will have the values of your system in
build/.../var/adm/cache/$pkg.
Yours,
--
René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
http://exactcode.de | http://t2-project.org | http://rene.rebe.name
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
