Package Details: atlas-lapack 1:3.10.3-9

Git Clone URL: https://aur.archlinux.org/atlas-lapack.git (read-only, click to copy)
Package Base: atlas-lapack
Description: Automatically Tuned Linear Algebra Software
Upstream URL: http://math-atlas.sourceforge.net
Licenses: BSD, custom:lapack
Provides: atlas-lapack-base, blas, cblas, lapack
Submitter: ilpianista
Maintainer: henkm
Last Packager: henkm
Votes: 93
Popularity: 0.001862
First Submitted: 2008-04-24 01:36 (UTC)
Last Updated: 2024-02-01 12:28 (UTC)

Required by (545)

Sources (4)

Pinned Comments

phcerdan commented on 2017-06-08 06:48 (UTC) (edited on 2017-06-08 06:49 (UTC) by phcerdan)

Hey I just installed, and make these notes, that might be useful for somebody else: Good explanation in atlas site: http://math-atlas.sourceforge.net/atlas_install/node5.html Follow this, the governor set by cpupower knows shit about CPU without this: http://unix.stackexchange.com/questions/121410/setting-cpu-governor-to-on-demand-or-conservative Summary: http://vincent.jousse.org/tech/archlinux-compile-lapack-atlas-kaldi/ ===========Steps=========== Permanent disable intel_pstate: Edit: /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="intel_pstate=disable" and update grub: grub-mkconfig -o /boot/grub/grub.cfg And then enable acpi-cpufreq module: su root echo "acpi-cpufreq" > /etc/modules-load.d/acpi-cpufreq.conf restart. Now cpupower can set frequencies properly. To disable throtling sudo pacman -S cpupower sudo cpupower frequency-set -g performance It should apply to all cores, but if it only apply to the first one: copy files to the other (4 in laptop) sudo cp /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor To restore: sudo cpupower frequency-set -g ondemand If not all cores are set: sudo cp /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor This stuff is only required at build time.

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 17 Next › Last »

Archange commented on 2015-12-29 11:34 (UTC)

Does not work for me. Question: is anyone here using intel-pstate as governor? Or are you guys using cpufreq?

jose1711 commented on 2015-12-28 20:12 (UTC)

ok, i take it back. did cpupower frequency-set -g performance and it compiled fine

Archange commented on 2015-12-27 21:53 (UTC)

@jose1711: I have the same issue on my laptop, on my server, on a friend laptop… And nothing I’ve tried to disable throttling worked in regard to compiling ATLAS…

jose1711 commented on 2015-12-27 21:49 (UTC)

Parallel make command configured as '$(MAKE) -j 2' CPU Throttling apparently enabled! It appears you have cpu throttling enabled, which makes timings unreliable and an ATLAS install nonsensical. Aborting. See ATLAS/INSTALL.txt for further information xconfig exited with 1

giniu commented on 2015-11-14 20:23 (UTC)

Thanks, I will check it out.

greyltc commented on 2015-11-14 10:19 (UTC) (edited on 2015-11-14 10:21 (UTC) by greyltc)

Hi giniu, could you please have a look at the recent change in atlas-lapack-base: https://projects.archlinux.org/svntogit/community.git/commit/trunk?h=packages/atlas-lapack-base&id=3cf00de8e4fc80a2e67b1b7348b425da3d5279e4 which was made to fix: https://bugs.archlinux.org/task/47049 and make the same change here? Thanks.

piratejon commented on 2015-10-22 00:09 (UTC)

I am getting a different MD5 for atlas3.10.2.tar.bz2 which is 0103b909e19ca9c6497a7ae696c16480

Archange commented on 2015-10-14 22:48 (UTC)

I’m having trouble w.r.t. disabling cpu throttling. Build fails on: CPU Throttling apparently enabled! It appears you have cpu throttling enabled, which makes timings unreliable and an ATLAS install nonsensical. Aborting. I’ve set all the core to performance, force them to be at their maximum frequency, but it still fails.

epitron commented on 2015-09-10 03:15 (UTC)

Strange issue: when the `afl` package is installed, ATLAS tries to use `afl-gcc` instead of `gcc`. I skimmed the configure script and the Makefile, and there doesn't seem to be anywhere it's searching for an alternative gcc executable. Passing congfigure the `--cc=gcc` option, or setting the CC environment variable to `CC=gcc` both have no effect. The simplest solution is to remove the `afl` package when you're building ATLAS. Does anyone have a better solution?