Source: atlas
Version: 3.8.4-9+deb7u1
Severity: normal
I tried to build a custom optimized version of the atlas libs, as
described in the file /usr/share/doc/libatlas3-base/README.Debian.
I got:
[9+0]atlas-3.8.4$ fakeroot debian/rules custom
rm -f configure-stamp
ncpu=$(LANG=C cpufreq-info | grep "analyzing CPU" -c);\
cpu=0;\
while test $cpu -lt $ncpu ; do\
if test $(cpufreq-info -p 2>&1 > /dev/null; echo $?) \
-eq 0 -a -z "$(LANG=C cpufreq-info -p -c $cpu | grep
performance)" ; then \
echo "frequency governor on cpu=$cpu is not set to
'performance'"; \
echo "run: 'sudo cpufreq-set -g performance -c cpu#'
for each cpu"; \
echo "aborting atlas build"; \
exit 1; \
fi; \
cpu=$((cpu+1)) ;\
done
# Here, the trick is pretty simple:
# * We don't want to build all the optimized version of Atlas. Just the
# one for the current CPU
# * We override ARCHS by base__
# * Base is the name of the package (libatlas3-base)
# * __ is provided to have the right expression
# * the regexp will consider that atlasArch and atlasISA are empty
# therefor, leaving the choice of the optimization to Atlas
# * After that, we fall back to the normal build procedure by calling
# debian/rules itself (yep, recursively)
# Remove all the other archs in this case
dch --local='+custom' "custom build on: `uname -a`"
/bin/sh: 1: dch: not found
make: *** [custom-stamp] Error 127
Searching on packages.debian.org, I see that the dch program is in the
devscripts package. Clearly devscripts should be in the Build-Depends
of atlas to avoid this problem.
-- System Information:
Debian Release: 7.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.10.59.3 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
