about "optimize" files

Thomas Pegg tom.pegg at gmail.com
Sat Nov 16 18:05:21 PST 2013

On 11/16/2013 4:29 AM, Pierre Labastie wrote:
> @Thomas:
>> I would agree but,  I would keep it noOpt by default as it is a safer
>> default, and keeps closer to by the book, if someone really wants to
>> optimize glibc they know they will want to and can override at their
>> discretion. I've learned from experience over optimization especially
>> with the core toolchain can create some very hard to track down bugs.
> Sure, but it is exactly what I propose: default to noOpt in opt_config. OTOH,
> opt_override is for people who change that default, in which case I propose to
> leave them free to not override optimization for all but gcc and grub.
Ahh, I must have misunderstood your original message a bit then. Sounds 
like a better setup than what is currently the default.
>>>    Now, the opt_config file. I'd like to ship it with MAKFLAGS="-j5"
>>> (quadricore CPUs are very common these days)
>> True, their common but your assuming that most are building on current
>> hardware, which I don't believe to be the case. I personally have always
>> put linux on older boxes, and most systems I have access to are only dual
>> core, so -j5 would be a bad default in that case.
> Agreed too. We are taking that to the menuconfig interface, with default -j1.
I like this too. :)

More information about the alfs-discuss mailing list