Package Details: atlas-lapack 3.10.3-4

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
Conflicts: atlas-lapack-base, blas, cblas, lapack, openblas, openblas-lapack
Provides: atlas-lapack-base, blas, cblas, lapack
Submitter: ilpianista
Maintainer: a.kudelin
Last Packager: a.kudelin
Votes: 92
Popularity: 0.181534
First Submitted: 2008-04-24 01:36
Last Updated: 2019-11-15 18:37

Required by (315)

Sources (3)

Latest Comments

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

giniu commented on 2015-04-24 09:14

it takes well too long. Can you somehow pass me the file that is mentioned in this log? I.e. error_<ARCH>.tgz - there are all informations about how configure went and what decisions were taken during build, so it would help a lot.

mutor commented on 2015-04-24 08:55

Build is failing for gcc 4.9.2, and is it supposed to take 7 hours? my CPU is AMD 8350 8-core. Log is following:

gcc version 4.9.2 20150304 (prerelease) (GCC)
/usr/bin/x86_64-unknown-linux-gnu-gcc-4.9.2 -V 2>&1 >> bin/INSTALL_LOG/ERROR.LOG
x86_64-unknown-linux-gnu-gcc-4.9.2: error: unrecognized command line option ‘-V’
x86_64-unknown-linux-gnu-gcc-4.9.2: fatal error: no input files
compilation terminated.
Make.top:4: recipe for target 'error_report' failed
make[4]: [error_report] Error 1 (ignored)
/usr/bin/x86_64-unknown-linux-gnu-gcc-4.9.2 --version 2>&1 >> bin/INSTALL_LOG/ERROR.LOG
tar cf error_AMDDRIVER64AVXMAC.tar Make.inc bin/INSTALL_LOG/*
bzip2 error_AMDDRIVER64AVXMAC.tar
make[4]: Leaving directory '/var/cache/pacman/pkg/atlas-lapack2194/atlas-lapack/src/ATLAS/build'
make[3]: Leaving directory '/var/cache/pacman/pkg/atlas-lapack2194/atlas-lapack/src/ATLAS/build'
make[2]: Leaving directory '/var/cache/pacman/pkg/atlas-lapack2194/atlas-lapack/src/ATLAS/build/bin'
Error report error_<ARCH>.tgz has been created in your top-level ATLAS
directory. Be sure to include this file in any help request.
cat: ../../CONFIG/error.txt: No such file or directory
cat: ../../CONFIG/error.txt: No such file or directory
Make.top:15: recipe for target 'build' failed
make[1]: *** [build] Error 255
make[1]: Leaving directory '/var/cache/pacman/pkg/atlas-lapack2194/atlas-lapack/src/ATLAS/build'
Makefile:488: recipe for target 'build' failed
make: *** [build] Error 2

arojas commented on 2013-11-11 07:57

The build failure should be fixed with glibc 2.18-10

kyak commented on 2013-10-04 20:18

@Marbur thanks, adding "-D c -DWALL" only in PKGBUILD made it work for me!

MarBur commented on 2013-10-04 19:57

On further checking downgrading gcc isn't necessary.
Try first with only -D c -DWALL without pstate change or anything it might work.
I used pstate because I needed atlas badly and didn't have time to figure out all combinations of working and non-working.

And changing kernel cmdline is 2 minute work and one restart.
Maybe if you can turn off power sawing this isn't necessary but my frequency kept changing no matter what I did.

kyak commented on 2013-10-03 16:28

Hm, not only i have to downgrade GCC, but also need to change my kernel cmdline. Unfortunately, the upstream doesn't seem to react. And there is too much of a hassle to make all these changes. Could someone upload a package for x64?

sfpotter commented on 2013-10-01 23:17

I was having the same issue with this package. Following the instructions in MarBur's latest comment, including setting intel_pstate=disable, I was able to build the package without issue.

MarBur commented on 2013-09-19 15:14

Atlas compiles with GCC 4.7 if I configure it with -D c -DWALL in addition to other settings in PKGBUILD. This uses wall timer for timing meaning that computer mustn't be busy.
I also booted with intel_pstate=disable because processor frequency didn't stay at 3.4 Ghz on performance governor if intel_pstate was configuring frequency.

kyak commented on 2013-09-17 17:22

@MarBur that's one great bug report. Let's see how upstream responds.

giniu commented on 2013-09-17 17:11

I don't think this is related to package itself, I will monitor this issue upstream. Thanks for reporting.