On Wednesday 19 January 2005 22:31, you wrote: > On Wed, 19 Jan 2005 22:11:37 +0100 > > Alexander Mieland <[EMAIL PROTECTED]> wrote: > > The GU is *our* factor which uses gcc to calculate these GUs for > > the packages. > > Using the "gcj" USE flag approximatly doubles gcc compilation time > here. Wrong choice obviously.
We know this, and we are already thinking about another solutioen since a few days. > Anyway, even if you choose a package without USE flags, the idea > of getting figures from emerge.log is broken because you can't > take the effect of ccache into account (that, and the log > rotation issue that has already been pointed). The logrotation-thingy would be no problem. As it is now, I've already the solution for this in basc. But well, this needs to copy all emerge.log* to another place and chmod/chown it, so that basc can read them. > > Perhaps we can create a little benchmark-program which will be > > compiled when basc was run for the first time. This could also > > be an idea. > > Compiling something out of portage sounds more reliable, yes. Why > not simply bash, so that you can reuse figures from LFS? how should this exactly look like? I would download a source-tarball of a bash-version and place it into the basc-tarball. Then the ebuild should copy this bash-tarball to... yes where? /etc: no, /tmp: no...? Or should basc do this all at the first run (download the tarball, unpack it and compile it)? If yes, where in the directory-tree should basc do this all? -- http://de.gentoo-wiki.com Alexander Mieland (aka dma147) http://www.gentoo-stats.org Registered Linux-User #249600 http://www.php-programs.de GnuGPG-ID: 209D65B5 http://www.affen-in-not.de www.php-programs.de/dma147.asc
pgpcb9SF5lb2E.pgp
Description: PGP signature
