On Wed, 24 Jun 2015 07:50:07 -0400 Alec Ten Harmsel <a...@alectenharmsel.com> wrote:
> On Wed, Jun 24, 2015 at 01:13:40PM +0200, Alan McKinnon wrote: > > On 23/06/2015 15:05, behrouz khosravi wrote: > >> I am trying to remove all the default use flags and control them > >> manually. > > > > Here's some good advice: > > > > Don't do that. See below. > > Nonsense - do that. If your goal is to learn how stuff works and > you're already reasonably familiar with C/C++ so you can debug any > strange errors that can happen, have fun. Just don't think you'll get > any real work done ;). I don't advocate completely overriding the profile defaults, but I do it myself and have been for years. In terms of getting work done, I estimate it costs me roughly five minutes per month, but with a pretty large standard deviation -- most months it's zero. It helps a lot to keep an eye on the -dev group for any discussion of possibly changing defaults; when a default changes, it almost always means you're going to have to change some flag settings either globally or for a few packages. Be particularly vigilant about changes which might leave you up a creek without a paddle, e.g. @system stuff or networking stuff. It also will help to learn which posters here override profile settings with USE="-*". There are a few of us (sorry, I only have a vague mental list), and the threads we start are likely to have the same issues you may hit. And whenever you ask for help about *anything*, whether you think it has to do with USE flags or not, mention at the start you're overriding the defaults. You'll get more little lectures about not doing that, but it's much better than having a guru who's trying to help find out a dozen posts downthread that he's been on a wild goose chase. > Also, properly setting CPU_FLAGS_X86 is another thing that can > speed up software *if* said software supports any special instruction > sets. And thank $DIETY for app-portage/cpuinfo2cpuflags. Well, I guess it's better to thank mgorny.
