| 1 |
On Thu, Dec 10, 2015 at 07:46:51AM +0100, Stefan G. Weichinger wrote |
| 2 |
> Am 10.12.2015 um 05:50 schrieb waltdnes@××××××××.org: |
| 3 |
> |
| 4 |
> > CFLAGS="-O2 -march=native -fomit-frame-pointer -pipe -fno-unwind-tables -fno-asynchronous-unwind-tables" |
| 5 |
> > |
| 6 |
> > That's what I use, except for cross-compiling. For an explanation of |
| 7 |
> > the "unwind" flags, see thread... |
| 8 |
> > http://comments.gmane.org/gmane.linux.busybox/36695 from the busybox |
| 9 |
> > mailing list. And don't forget CPU_FLAGS_X86. Emerge and run |
| 10 |
> > app-portage/cpuinfo2cpuflags as soon as you can during the install |
| 11 |
> > process. I believe that's right after running "eselect profile". And |
| 12 |
> > then run "emerge system && emerge world". It's a lot quicker when you |
| 13 |
> > don't have very much installed on the machine. |
| 14 |
> |
| 15 |
> did not know that tool, thanks. |
| 16 |
> Will try on my existing box already. |
| 17 |
> |
| 18 |
> Do I have to set that variable then (in make.conf?) ? |
| 19 |
|
| 20 |
Yes, you should. While you're at it, you can remove the corresponding |
| 21 |
flags from the USE= variable. I don't know if they're honored by |
| 22 |
portage any longer. I assume you missed the news item back in January. |
| 23 |
It's archived and you can read it at... |
| 24 |
https://www.gentoo.org/support/news-items/2015-01-28-cpu_flags_x86-introduction.html |
| 25 |
|
| 26 |
-- |
| 27 |
Walter Dnes <waltdnes@××××××××.org> |
| 28 |
I don't run "desktop environments"; I run useful applications |
Archives