Hi, On Thu, Aug 20, 2015 at 11:58 PM, Cyril Hrubis <chru...@suse.cz> wrote:
> Hi! > > # Do any CPU support cpufreq? > > -#CPUFREQ_ENABLED_CPUS=`/bin/ls -lad > /sys/devices/system/cpu/cpu*/cpufreq 2> /dev/null | wc -l` > > +CPUFREQ_ENABLED_CPUS=`/bin/ls -lad /sys/devices/system/cpu/cpu*/cpufreq > 2> /dev/null | wc -l` > > Calling ls by full path is simply wrong. > ok. > > > -#if [ "$CPUFREQ_ENABLED_CPUS" -lt 1 ]; then > > -# echo "None of your CPUs support cpufreq. Bye." > > -# exit 255 > > -#fi > > +if [ "$CPUFREQ_ENABLED_CPUS" -lt 1 ]; then > > + echo "None of your CPUs support cpufreq. Bye." > > + exit 255 > > +fi > > This part of code was specially disabled in one commit, unfortunately it > does not say why exactly it was disabled. So I'm hesitant to enable it > unless we are sure that the code actually works fine on several > distributions. > Yes, it also make me confused. but I found another place always using the same codes for a long time. ".../pounder21/build_scripts/cpufreq" <----- this file do the same check before compile the cpufreq package. So, I feel that wouldn't have any pernicious influence on pounder21. > -- > Cyril Hrubis > chru...@suse.cz > -- Regards, Li Wang Email: liw...@redhat.com
------------------------------------------------------------------------------
_______________________________________________ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
