> I sure can do that so that when GCC version goes to 4.5, for example, 
> and everything still works fine, developers aren't confused as to why we 
> like an older version GCC. If GCC 4.5 breaks things, then we can have 
> gcc4 to mean from 4.0 to a new specific version number (gcc45), if 
> available. (It is risky to rename SYSTEM_ID for stable projects just 
> because developers' machines are upgraded over time.)
> 
> If I were to do that, should I use "glibc2" (as opposed to glibc24) too?

Sure.

> 
>> and change i486 to x86 or
> 
> I need to keep i486, because LSB 3.1 always target i486, or it is not 
> LSB 3.1 compliant.
> 
> This configuration file hard code the machine architecture compiler 
> switches to i486.

Have we looked at how this might affect performance?

--greg.


> 
> Thanks.
> 
>> something like that. Just be sure to document it at the top
>> of the file.
>>
>> --greg.
>