At 02:49 PM 1/19/2007, Greg Wright wrote:
>Daniel Yek wrote:
>>Hi,
>>I'm creating a new configuration, a new SYSTEM_ID for Helix and 
>>RealPlayer build in LSB chroot build environment (BE).
>>I have been using:
>>   linux-2.6-glibc24-gcc41-i486-lsb
>>as the new system id.
>>The new configuration file would be:
>>$BUILD_ROOT/umakecf/linux-2.6-glibc24-gcc41-i486-lsb.cf
>>Anybody has an opinion if I should be naming the new SYSTEM_ID 
>>differently, likes just use "glibc2", rather than "glibc24", or use 
>>"gcc40" or "gcc4" rather than "gcc41"?
>>Thanks.
>
>What you have is fine. I think we need to look at all of
>our .cf files at some point. They are not all named in
>a consistent way, sometimes not even accurate.
>
>If you wanted I would say use gcc4

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?

>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.

Thanks.

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

-- 
Daniel Yek