>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".
--
View this message in context:
http://www.nabble.com/TMPFS-out-of-disk-space-workaround-feature-suggestion-tp22688139p22738036.html
Sent from the T2 mailing list archive at Nabble.com.
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
