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.001683
First Submitted: 2008-04-24 01:36 (UTC)
Last Updated: 2024-02-01 12:28 (UTC)

Required by (548)

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 .. 12 13 14 15 16 17

mickele commented on 2010-10-19 07:05 (UTC)

@darenw I am working on a new PKGBUILD that should solve your problem. It builds twice the library: the first time without option "-fPIC" for static library, and the second time with "-fPIC" to build shared ones. Now I am testing the package, I think I'll upload this new version in a few days.

<deleted-account> commented on 2010-10-07 00:01 (UTC)

Problem semi-solved! There was a old stray .a w/o accompanying .so files in /usr/local/lib, while the good newly built files were installed in /usr/lib. CMake picked up on the stray. This was easy to fix, and compilation now goes past that point... only to find a similar situation with another library. Bottom line: okay, atlas-lapack is innocent of any wrongdoing.

<deleted-account> commented on 2010-10-06 15:19 (UTC)

Wish I could, but the build system, which is itself massively complex in this project, insists on static. I will find some way to fool it...

jedbrown commented on 2010-10-06 10:22 (UTC)

You should not be trying to link a static archive into a shared library, use the shared liblapack.so or link the whole thing statically.

<deleted-account> commented on 2010-10-06 08:44 (UTC)

Looks like -fPIC is needed somewhere in PKGBUILD. In bulding a large app depending on atlas/lapack/blas, I couldn't create an .so due to it wanting to link liblapack.a, but apparently the .a files made by this package aren't made with -fPIC.

<deleted-account> commented on 2010-08-03 08:33 (UTC)

Required also by scalapack

mickele commented on 2010-04-19 21:27 (UTC)

@luismiguelgcg I agree with giniu. If you need the latest unstable atlasyou should create package atlas-lapack-dev, atlas-lapack refers only to the latest stable version.

giniu commented on 2010-04-19 20:59 (UTC)

I think 3.9 is unstable branch, isn't it? Atlas braks too often by itself and many apps are not 3.9 ready, so maybe atlas-lapack-dev would be better? I'd say stick with 3.8 for this :)

luismiguelgcg commented on 2010-04-19 20:45 (UTC)

Latest upstream version is 3.9.23.