The following USE changes are necessary to proceed: (see "package.use" in the portage(5) man page for more details) # required by sys-devel/clang-3.3-r100 # required by @selected # required by @world (argument) =sys-devel/llvm-3.3-r1 clang I think it'd be a lot easier if it were just default-enabled
I thought about this too but there's a big cons -- all those mesa users who need only LLVM (because of mesa) and are going to hit 2.4G multilib llvm+clang build.
$ equery s llvm * sys-devel/llvm-3.3-r1 Total files : 1307 Total size : 616.49 MiB it's not that big anyway ;) I guess this is a situation where you can't make everyone happy - I had to enable the useflag on all machines that have llvm installed, and I wouldn't be upset about a few megabytes extra.
Errr... nostrip? * sys-devel/llvm-9999-r1 Total files : 1532 Total size : 269.65 MiB But I was referring to the build tree size. 2.4G is the amount that exceeds tmpfs for many people and requires special action. Enabling a USE flag is IMO easier than knowing that you can disable USE=clang without making mesa sad.
People using tmpfs should not be a reason ... (Plus there's packages like boost that need >9GB anyway, so ... why do we care about self-inflicted failures?)
(In reply to Patrick Lauer from comment #4) > People using tmpfs should not be a reason ... Shouldn't people with recommended setup by a main reason for defaults? > (Plus there's packages like boost that need >9GB anyway, so ... why do we > care about self-inflicted failures?) I'm sorry but I must be using the wrong boost then since my boost is much smaller (and faster to build) than llvm.
