DISTCC

[Kok, Auke]

samuel wrote:
> should prolly be DISTCC_SAFE :) will do that when i start patching :)

other than that looks OK to me!

Auke


> 
> On Jan 8, 2008 9:43 AM, samuel <samuel.verstraete at gmail.com> wrote:
>> Hi,
>>
>> I patched the distcc-optimizations.plugin so it follows a flag in the
>> DETAILS file on distcc saveness...
>>
>> All that is required is that, like for PSAFE, you add the
>> DISTCC_SAFE="no" to the DETAILS file.
>>
>> patch for the distcc-optimization.plugin:
>>
>>
>> root at gisoil13 /var/lib/lunar/plugins # diff -u
>> /var/lib/lunar/moonbase/distributed/distcc/plugin.d/optimize-distcc.plugin
>> optimize-distcc.plugin
>> --- /var/lib/lunar/moonbase/distributed/distcc/plugin.d/optimize-distcc.plugin  2007-10-10
>> 13:01:01.000000000 +0200
>> +++ optimize-distcc.plugin      2008-01-08 09:40:55.519653117 +0100
>> @@ -8,20 +8,25 @@
>>         if [ -f /etc/lunar/local/optimizations.DISTCC ]; then
>>                 . /etc/lunar/local/optimizations.DISTCC
>>         fi
>> -
>> -       if [ "$USE_DISTCC" == "yes" ]; then
>> -               # we append distcc in case ccache is also used to
>> -               # make sure that distcc goes first!
>> -               echo $CC_EXT | grep -q "distcc" || CC_EXT="$CC_EXT distcc"
>> -               echo $CXX_EXT | grep -q "distcc" || CXX_EXT="$CXX_EXT distcc"
>> -               export CC_EXT
>> -               export CXX_EXT
>> -               export DISTCC_HOSTS
>> -               export DISTCC_ALLOW
>> -               verbose_msg "CC_EXT=\"$CC_EXT\""
>> -               verbose_msg "CXX_EXT=\"$CXX_EXT\""
>> -               verbose_msg "DISTCC_HOSTS=\"$DISTCC_HOSTS\""
>> -               verbose_msg "DISTCC_ALLOW=\"$DISTCC_ALLOW\""
>> +
>> +       if [ "$DISTCC_SAVE" = "no" ]; then
>> +               message "${CYAN}This module is not distcc-safe,"
>> +               message "so it will be compiled without distcc.${DEFAULT_COLOR}"
>> +       else
>> +               if [ "$USE_DISTCC" == "yes" ]; then
>> +                       # we append distcc in case ccache is also used to
>> +                       # make sure that distcc goes first!
>> +                       echo $CC_EXT | grep -q "distcc" || CC_EXT="$CC_EXT distcc"
>> +                       echo $CXX_EXT | grep -q "distcc" || CXX_EXT="$CXX_EXT distcc"
>> +                       export CC_EXT
>> +                       export CXX_EXT
>> +                       export DISTCC_HOSTS
>> +                       export DISTCC_ALLOW
>> +                       verbose_msg "CC_EXT=\"$CC_EXT\""
>> +                       verbose_msg "CXX_EXT=\"$CXX_EXT\""
>> +                       verbose_msg "DISTCC_HOSTS=\"$DISTCC_HOSTS\""
>> +                       verbose_msg "DISTCC_ALLOW=\"$DISTCC_ALLOW\""
>> +               fi
>>         fi
>>         return 2
>>  }
>>
>> I know that we don't want to add too much stuff in the DETAILS file
>> but this is only for very few modules... i'm guessing about 20
>> modules, i can gain a lot of time by setting that flag.
>>
>>
>> If no one objects i will proceed tagging modules with this new flag.
>>
>> cheers,
>>
>> Samuel
>>
> _______________________________________________
> Lunar-dev mailing list
> Lunar-dev at lunar-linux.org
> http://foo-projects.org/mailman/listinfo/lunar-dev