Summary: | CFLAGS & CXXFLAGS vs profile | ||
---|---|---|---|
Product: | [OLD] Docs on www.gentoo.org | Reporter: | Jacob Lindberg <jni> |
Component: | Installation Handbook | Assignee: | Docs Team <docs-team> |
Status: | VERIFIED INVALID | ||
Severity: | enhancement | CC: | radek |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jacob Lindberg
2006-04-19 00:36:28 UTC
1 month and no response. looks to me like the info is already there Choosing the Right Profile First, a small definition is in place. A profile is a building block for any Gentoo system. Not only does it specify default values for CHOST, CFLAGS and other important variables, it also locks the system to a certain range of package versions. This is all maintained by the Gentoo developers. Yes I know that, but my point was that nowhere is it stated that your own make.conf is overruling the default profile, like the CFLAGS and CXXFLAGS variables. I didn't mean a rewrite of the handbook, just perhaps a footnote concerning this. Something like: 'Keep in mind that all settings from your default profile, is overruled/overwritten by the settings placed in your make.conf'. Like if you don't know what you are doing, don't play with make.conf. See what I mean or is it just bologni? i dont see much value in explicitly stating that ... the profile and such files are described as setting up default values ... so when you configure make.conf in chapter 5, the implicit meaning is that you're overriding any and all default values Okay, I rest my case :-) Closing. |