1 |
While at it, it might be useful to have someghing like compiler-use file |
2 |
( like package.use) for per-package compiler version and FLAGS to be used. |
3 |
|
4 |
It is annoying to have emerge -eD world fail because some package |
5 |
requires specific compiler version or because gcc-3.4 can't be compiled |
6 |
with -march=barcelona or with -combine CFLAGS... |
7 |
There should also be an option for the user to match compiler with |
8 |
compiler version, used to compile some other package. Perhaps with |
9 |
naming full name of the package instead of compiler name and version |
10 |
string in some file, like /etc/portage/package-infra.use or something |
11 |
like that. |
12 |
|
13 |
That approach could also be used for selecting specific version of |
14 |
perl/python/ruby/autotools/whatnot. |
15 |
|
16 |
|
17 |
|
18 |
|
19 |
|
20 |
|
21 |
|
22 |
|
23 |
ederico Ferri wrote: |
24 |
> -----BEGIN PGP SIGNED MESSAGE----- |
25 |
> Hash: SHA1 |
26 |
> |
27 |
> Hello, |
28 |
> today I hit this annoyance, because my laptop hung in the middle of an |
29 |
> 'emerge -e @world' (checking that my world set compiles with |
30 |
> gcc-4.3... stopped at ~ 300 of 700 :S ) |
31 |
> |
32 |
> I was looking for an entry in /var/db/pkg/<cat/pkg>/ that could have |
33 |
> told me the compiler used to build the package, but couldn't find any. |
34 |
> indeed it would be a fairly useful feature to have, both for testing |
35 |
> purposes, and for user's everyday maintenance. |
36 |
> |
37 |
> please criticize this with anything constructive you can think of. |
38 |
> |
39 |
> thanks |
40 |
> - -- |
41 |
> Federico Ferri |
42 |
> -----BEGIN PGP SIGNATURE----- |
43 |
> Version: GnuPG v2.0.9 (GNU/Linux) |
44 |
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
45 |
> |
46 |
> iEYEARECAAYFAkk9v14ACgkQV/B5axfzrPucugCfRN51KpJZ/HYCYA3v/Z2lAhaf |
47 |
> 8eUAniZONnbWtN4f5CblJzaxEMbFWI3m |
48 |
> =4l7H |
49 |
> -----END PGP SIGNATURE----- |
50 |
> |
51 |
> |
52 |
> |
53 |
> |
54 |
> |