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

Required by (550)

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 2 3 4 5 6 7 .. 18 Next › Last »

pryow commented on 2023-07-22 06:10 (UTC) (edited on 2023-07-22 06:10 (UTC) by pryow)

Hi, I am getting a similar error as others.

I have already disabled CPU frequency scaling with "sudo cpupower frequency-set -g performance", but am still getting the same error.

How might I resolve this? (Error below)

OS configured as UNKNOWN (0) xconfig: /home/user/.cache/yay/atlas-lapack/src/ATLAS/build/..//CONFIG/src/config.c:602: ProbeOS: Assertion `iret' failed. /bin/sh: line 1: 118028 Aborted (core dumped) ./xconfig -d s /home/user/.cache/yay/atlas-lapack/src/ATLAS/build/../ -d b /home/user/.cache/yay/atlas-lapack/src/ATLAS/build -D c -DATL_DYLIBS -Si lapackref 1 -D c -DATL_FULL_LAPACK xconfig exited with 134 ==> ERROR: A failure occurred in build(). Aborting... -> error making: atlas-lapack-exit status 4 -> Failed to install the following packages. Manual intervention is required: atlas-lapack - exit status 4

henkm commented on 2023-07-12 11:57 (UTC)

konaaa, you need to look in the comments below how to disable cpu throttling, including disabling pstate if you're on an intel cpu. No need to hack anything for that.

konaaa commented on 2023-07-03 03:36 (UTC) (edited on 2023-07-03 03:37 (UTC) by konaaa)

I managed to solve the fgrep comment but i have another error


Maximum number of threads configured as 8 /usr/bin/ld: probe_pmake.o: en la función ATL_tmpnam': /home/martins/.cache/yay/atlas-lapack/src/ATLAS/build/..//CONFIG/src/probe_pmake.c:224: aviso: the use oftmpnam' is dangerous, better use `mkstemp' Parallel make command configured as '$(MAKE) -j 8' ERROR: enum fam=3, chip=2, mach=0 make[3]: *** [Makefile:107: atlas_run] Error 44 make[2]: *** [Makefile:405: IRunArchInfo_x86] Error 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 ==> ERROR: Se produjo un fallo en build(). Cancelando... -> error compilando: atlas-lapack-exit status 4 -> Ha fallado al instalar los siguientes paquetes. Una intervención manual es requerida: atlas-lapack - exit status 4 [martins@pog ~]$


I'm going to download the atlas-lapack .tar to review the installation file and see what I can do, but I could use some help.

konaaa commented on 2023-07-03 02:07 (UTC) (edited on 2023-07-03 02:36 (UTC) by konaaa)

Hello, sorry for the format of the comment but I don't know how to highlight it.

I'm trying to install SExtractor and it asks me for atlas libraries

I have the following error when I try to perform yay atlas-lapack

Does anyone know how to fix it? I'm new to this and I really don't have much idea


home/martins/.cache/yay/atlas-lapack/src/ATLAS/build/..//CONFIG/src/probe_OS.c:224: aviso: the use of tmpnam' is dangerous, better usemkstemp'

Bad OS value=0, res='*��\'

OS configured as UNKNOWN (0) xconfig: /home/martins/.cache/yay/atlas-lapack/src/ATLAS/build/..//CONFIG/src/config.c:602: ProbeOS: Assertion iret' failed. /bin/sh: línea 1: 2326108 Abortado (core' generado) ./xconfig -d s /home/martins/.cache/yay/atlas-lapack/src/ATLAS/build/../ -d b /home/martins/.cache/yay/atlas-lapack/src/ATLAS/build -D c -DATL_DYLIBS -Si lapackref 1 -D c -DATL_FULL_LAPACK xconfig exited with 134 ==> ERROR: Se produjo un fallo en build(). Cancelando... -> error compilando: atlas-lapack-exit status 4 -> Ha fallado al instalar los siguientes paquetes. Una intervención manual es requerida: atlas-lapack - exit status 4


I think the solution is in one of the comments below, but being new i don't understand how i have to do it

Any help is greatly appreciated, i really need to install sextractor c:

henkm commented on 2023-06-29 06:57 (UTC) (edited on 2023-06-29 07:19 (UTC) by henkm)

I get a segfault during building:

80 of /home/henk/aur/atlas-lapack/src/ATLAS/build/..//include/atlas_mmtesttime.h: FAILED COMMAND : make mmutstcase mmrout=CASES/ATL_dmm4x2x256_avx.c beta=-1 betan="N1" DMC="/usr/bin/x86_64-linux-gnu-gcc -O -fomit-frame-pointer -mavx -m64 -fPIC -m64 -fPIC" DMCFLAGS="-x assembler-with-cpp -mavx" pre=d M=56 N=56 K=56 mb=0 nb=0 kb=56 lda=64 ldb=72 ldc=116 > /dev/null 2>&1

80 of /home/henk/aur/atlas-lapack/src/ATLAS/build/..//include/atlas_mmtesttime.h: FAILED COMMAND : make mmutstcase mmrout=SSEGENOUTDIR/dgenmm_sse.c beta=0 pre=d M=26 N=26 K=26 mb=26 nb=26 kb=26 lda=26 ldb=26 ldc=56 > /dev/null 2>&1

ETA: actually 3 SIGSEGV, 2 SIGILL and 2 SIGABRT

a.kudelin commented on 2023-04-03 12:07 (UTC)

Disowning because I don't have enough resources to build it.

frazar0 commented on 2023-02-24 09:03 (UTC)

I was getting an error of the form

$ ../configure --prefix=/usr --shared --with-netlib-lapack-tarfile=~/atlas/lapack-3.11.0.tar.gz
make: 'xconfig' is up to date.
./xconfig -d s /home/frazar/atlas/src/ATLAS/build/../ -d b /home/frazar/atlas/src/ATLAS/build  -D c -DATL_DYLIBS -Si lapackref 1

Bad OS value=0, res='�'

This appears due to the "xconfig" binary internally piping "fgrep" output to a temporary file and stumbling on the recently-introduced obsolence warning

fgrep: warning: fgrep is obsolescent; using grep -F
OS=1

Fixed by commenting the warning line in /usr/bin/fgrep.

ColonelThirtyTwo commented on 2022-05-25 20:12 (UTC)

The throttle check attempts to read from /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq, which has 0200 permissions, so it will never pass.

Here's a dumb patch to fix it.

--- a/CONFIG/src/backend/archinfo_linux.c   2016-07-28 15:43:01.000000000 -0400
+++ b/CONFIG/src/backend/archinfo_linux.c   2022-05-25 16:01:07.285107438 -0400
@@ -562,9 +562,9 @@
       res = atlsys_1L(NULL,
             "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor", 0, 0);
       assert(res);
-      if (icur < imax)
-         iret = 1;
-      else if (!strstr(res, "performance") && imin < imax)
+//      if (icur < imax)
+//         iret = 1;
+      /*else*/ if (!strstr(res, "performance") && imin < imax)
          iret = 1;
       free(res);
    }

Marcello commented on 2022-04-20 16:22 (UTC) (edited on 2022-04-20 16:30 (UTC) by Marcello)

ISSUE SOLVED

both for marcello https://aur.archlinux.org/packages/atlas-lapack#comment-858687

and for bug-reaper https://aur.archlinux.org/packages/atlas-lapack#comment-747840

For the library to compile you need not only two fix the blas/C/testing/ directory as described in File: gfortran-10.patch but also fix the two equivalent files in blas/F77/ , in such way that you have:

[ATLAS3.10.3]$ grep -rnF ",STEMP,"

src/blas/f77reference/srotmg.f:55: + SQ2,STEMP,SU,TWO,ZERO

interfaces/blas/C/testing/c_dblat1.f:250: CALL STEST1(DNRM2TEST(N,SX,INCX),STEMP(1),STEMP,SFAC)

interfaces/blas/C/testing/c_dblat1.f:254: CALL STEST1(DASUMTEST(N,SX,INCX),STEMP(1),STEMP,SFAC)

interfaces/blas/C/testing/c_sblat1.f:250: CALL STEST1(SNRM2TEST(N,SX,INCX),STEMP(1),STEMP,SFAC)

interfaces/blas/C/testing/c_sblat1.f:254: CALL STEST1(SASUMTEST(N,SX,INCX),STEMP(1),STEMP,SFAC)

interfaces/blas/F77/testing/dblat1.f:313: CALL STEST1(DNRM2(N,SX,INCX),STEMP(1),STEMP,SFAC)

interfaces/blas/F77/testing/dblat1.f:317: CALL STEST1(DASUM(N,SX,INCX),STEMP(1),STEMP,SFAC)

interfaces/blas/F77/testing/sblat1.f:313: CALL STEST1(SNRM2(N,SX,INCX),STEMP(1),STEMP,SFAC)

interfaces/blas/F77/testing/sblat1.f:317: CALL STEST1(SASUM(N,SX,INCX),STEMP(1),STEMP,SFAC)

Important: you also need to restart clean and build, otherwise you still get a segmentation fault error.

Marcello commented on 2022-03-28 12:08 (UTC) (edited on 2022-03-28 12:20 (UTC) by Marcello)

I had failure during make check similarly to what bug-reaper reports: https://aur.archlinux.org/packages/atlas-lapack#comment-747840

Has something to do with newer gcc/gcc-libs/gcc-fortran. I downgraded to 8.3 for each and it installed no problem. Not sure how you would handle this in a PKGBUILD

I essentially did what I reported in https://bbs.archlinux.org/viewtopic.php?pid=2028537#p2028537

$ git clone https://aur.archlinux.org/gcc9.git

$ makepkg -si

$ export CC="/usr/bin/gcc-9"

$ export CXX="/usr/bin/g++-9"

$ yay atlas-lapack

when I thought it would have been enough to go back to gcc9

but then it fails again with the same error

The reason could be this. The log shows that the exports had no effect, because it uses:

/usr/bin/x86_64-pc-linux-gnu-gcc

while alongside on the same dir there's also

/usr/bin/x86_64-pc-linux-gnu-gcc-9

which is what I probably need, and other versions.

What should I do?

Should I also avoid yay and follow instructions like in the section 'Configuring, building and installing' of https://www.astr.tohoku.ac.jp/~akhlaghi/ATLAS_install.html ?