| 1 |
Neil Bothwick wrote: |
| 2 |
> On Sat, 08 Jul 2006 02:00:27 +0300, Daniel Iliev wrote: |
| 3 |
|
| 4 |
> emerge is, by definition, a non-interactive program (apart from --ask |
| 5 |
> which works before emerge starts its business). Use the ELOG features of |
| 6 |
> portage 2.1 to have this messages save to a file, mailed to you or read |
| 7 |
> out with festival. |
| 8 |
|
| 9 |
As I already replied to Mr Justin R Findlay's email "ELOG" is something |
| 10 |
new to me. I have to check it out. Thank you for pointing this out. |
| 11 |
|
| 12 |
> |
| 13 |
> EXTRA_ECONF="--disable-runtime-cpudetection" emerge --options mplayer |
| 14 |
> |
| 15 |
> This doesn't work with every ebuild, but it does with most of them. |
| 16 |
> |
| 17 |
|
| 18 |
Correct. This doesn't work for mplayer. |
| 19 |
|
| 20 |
|
| 21 |
> If it is know that the package will fail with -O3, what is the point of |
| 22 |
> letting it through, even if it warns you. However, an einfo message |
| 23 |
> whenever CFLAGS are overridden would be nice. |
| 24 |
> |
| 25 |
|
| 26 |
Well, I can't imagine that gentoo maintainers have the opportunity to |
| 27 |
check all the possible combinations of flags and system setting before |
| 28 |
they release an ebuild. It is of course better that they prefer to use |
| 29 |
the "safe way". |
| 30 |
I thing an einfo message is the least thing they could give us, though I |
| 31 |
prefer to have the choice to try the aggressive setting and if they |
| 32 |
don't work for me to revert to the recommended flags. |
| 33 |
|
| 34 |
|
| 35 |
-- |
| 36 |
Best regards, |
| 37 |
Daniel |
| 38 |
|
| 39 |
-- |
| 40 |
gentoo-user@g.o mailing list |
Archives