While at it, it might be useful to have someghing like compiler-use file
( like package.use) for per-package compiler version and FLAGS to be used.
It is annoying to have emerge -eD world fail because some package
requires specific compiler version or because gcc-3.4 can't be compiled
with -march=barcelona or with -combine CFLAGS...
There should also be an option for the user to match compiler with
compiler version, used to compile some other package. Perhaps with
naming full name of the package instead of compiler name and version
string in some file, like /etc/portage/package-infra.use or something
like that.
That approach could also be used for selecting specific version of
perl/python/ruby/autotools/whatnot.
ederico Ferri wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
today I hit this annoyance, because my laptop hung in the middle of an
'emerge -e @world' (checking that my world set compiles with
gcc-4.3... stopped at ~ 300 of 700 :S )
I was looking for an entry in /var/db/pkg/<cat/pkg>/ that could have
told me the compiler used to build the package, but couldn't find any.
indeed it would be a fairly useful feature to have, both for testing
purposes, and for user's everyday maintenance.
please criticize this with anything constructive you can think of.
thanks
- --
Federico Ferri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkk9v14ACgkQV/B5axfzrPucugCfRN51KpJZ/HYCYA3v/Z2lAhaf
8eUAniZONnbWtN4f5CblJzaxEMbFWI3m
=4l7H
-----END PGP SIGNATURE-----