I have an amd processor. I followed the @phcerdan's comment with no success. I also try to disable pstate for my cpu with amd_pstate and amp_pstate_epp but couldn't make it work.
Search Criteria
Package Details: atlas-lapack 1:3.10.3-9
Package Actions
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.002192 |
First Submitted: | 2008-04-24 01:36 (UTC) |
Last Updated: | 2024-02-01 12:28 (UTC) |
Dependencies (2)
- gcc-libs (gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-gitAUR)
- gcc-fortran (gccrs-fortran-gitAUR, gcc11-fortranAUR, gcc-fortran-gitAUR) (make)
Required by (544)
- abinit (requires blas)
- abinit (requires lapack)
- algodoo (requires lapack)
- ambertools (requires blas)
- ambertools (requires lapack)
- amino-git (requires cblas)
- amino-git (requires lapack)
- apbs (requires blas)
- apbs (requires lapack)
- armadillo (requires blas)
- armadillo (requires lapack)
- arpack++ (requires blas)
- arpack++ (requires lapack)
- arpack-git (requires lapack)
- arrayfire-git (requires cblas)
- atompaw (requires lapack)
- atomsk-git (requires blas)
- atomsk-git (requires lapack)
- avs-device-sdk (requires cblas)
- basix (requires lapack)
- Show 524 more...
Sources (4)
saliherdemk commented on 2024-03-26 13:43 (UTC)
henkm commented on 2024-03-25 05:20 (UTC)
@saliherdemk If you have an intel processor, did you disable p-state? Refer to the pinned comment for instructions.
saliherdemk commented on 2024-03-23 16:52 (UTC)
I've tried almost everything in the comment section to solve the CPU throttling issue, but I couldn't. I ran "sudo cpupower frequency-set -g performance", but the issue still persists. I'm tracking it with cpupower-gui, and it seems to be set as expected. I thought virtualization might be the problem. When I set it to performance, it complains about some CPUs being offline:
"12-31 cpupower set operation was not performed on them."
So I tried to disable it. I disabled it in BIOS but it didn't work. I also tried the following command:
"echo off | sudo tee /sys/devices/system/cpu/smt/control"
Any help would be appreciated.
henkm commented on 2024-02-07 01:46 (UTC) (edited on 2024-02-07 01:47 (UTC) by henkm)
@testovich I can't really see what's going on on your system so I can only offer you some guesses. Do you have some non-standard configuration regarding your (fortran) compiler? There are some remarks regarding that on https://math-atlas.sourceforge.net/errata.html
The easiest in that case would be to use a clean chroot with a standard makepkg.conf
There is also a conversation on the sourceforge page from 2009 with the same error message but the problem seems to have been resolved by the user without reporting back the solution.
ETA: the test on cpu throttling is one of the first things done. Since your build progressed to the tuning, there's no problem there.
testovich commented on 2024-02-06 23:07 (UTC) (edited on 2024-02-06 23:38 (UTC) by testovich)
After quite a long installation, I received the following message
ATLAS install complete. Examine
ATLAS/bin/<arch>/INSTALL_LOG/SUMMARY.LOG for details.
make[1]: Leaving directory '/home/user/Downloads/atlas/atlas-lapack/src/ATLAS/build'
make clean
make[1]: Entering directory '/home/user/Downloads/atlas/atlas-lapack/src/ATLAS/build'
rm -f *.o x* config?.out *core*
make[1]: Leaving directory '/home/user/Downloads/atlas/atlas-lapack/src/ATLAS/build'
make: *** No rule to make target 'libptf77blas.a', needed by 'libptf77blas.so'. Stop.
==> ERROR: A failure occurred in build().
Aborting...
Please tell me how to solve this problem?
p.s. I hope that I have configured the processor correctly? Result of the command
sudo cpupower frequency-info
analyzing CPU 0:
no or unknown cpufreq driver is active on this CPU
CPUs which run at the same hardware frequency: Not Available
CPUs which need to have their frequency coordinated by software: Not Available
maximum transition latency: Cannot determine or is not supported.
Not Available
available cpufreq governors: Not Available
Unable to determine current policy
current CPU frequency: Unable to call hardware
current CPU frequency: Unable to call to kernel
boost state support:
Supported: no
Active: no
henkm commented on 2024-02-01 12:32 (UTC) (edited on 2024-02-01 12:35 (UTC) by henkm)
I understand that commenting out the echo statement from /usr/bin/fgrep
is not a real solution. I tried to copy /usr/bin/fgrep
to /tmp/fgrep
and comment it out there, then change all occurrences of fgrep
in all files to /tmp/fgrep
but somehow that doesn't work. Maybe the path is not accessible from within the build environment? If someone can help me with that, I'd be grateful. For now, I just added a warning at the start for users to change it manually.
henkm commented on 2023-07-26 01:32 (UTC)
I realised that the recent commits changed the versions of both ATLAS and LAPACK. However, ATLAS 3.10.3 is still the latest stable release. The latest development release is 3.11.41, so 3.11.0 makes no sense at all. Keeping LAPACK at 3.11.0 and setting ATLAS back to 3.10.3 solves the compilation problem for me.
henkm commented on 2023-07-23 07:29 (UTC)
pryow, see frazar0's comment on 24 February this year. https://aur.archlinux.org/packages/atlas-lapack#comment-903477
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.
Pinned Comments
phcerdan commented on 2017-06-08 06:48 (UTC) (edited on 2017-06-08 06:49 (UTC) by phcerdan)