Package Details: atlas-lapack 3.10.2-3

Git Clone URL: (read-only)
Package Base: atlas-lapack
Description: Complete LAPACK and BLAS implementation using optimised ATLAS routines
Upstream URL:
Licenses: custom:blas, custom:lapack, custom:atlas
Conflicts: atlas-lapack-base, blas, cblas, lapack
Provides: atlas-lapack-base, blas, cblas, lapack=3.6.0
Submitter: ilpianista
Maintainer: giniu
Last Packager: giniu
Votes: 80
Popularity: 0.151279
First Submitted: 2008-04-24 01:36
Last Updated: 2016-02-25 10:53

Required by (163)

Sources (6)

Latest Comments

melissawm commented on 2016-06-11 21:27

Hi all,

I'm trying to build this package via makepkg in order to include it in CCR (chakra does not provide this package) and I get the following error:

cp: impossível obter estado de '/home/melissa/atlas_lapack_package_chakra/atlas-lapack/src/ATLAS/build/lib/libsatlas.dylib': Arquivo ou diretório não encontrado recipe for target 'install_lib' failed
make[1]: [install_lib] Error 1 (ignored)

Checking the make files I got this from Make.lib:

# =======================================================================
# The following commands are to build dynamib libraries on OS X (in BETA)
# =======================================================================
dylib :
rm -rf $(tmpd) ; mkdir $(tmpd)
cd $(tmpd) ; ar x ../liblapack.a
cd $(tmpd) ; ar x ../libf77blas.a
cd $(tmpd) ; ar x ../libcblas.a
cd $(tmpd) ; ar x ../libatlas.a
cd $(tmpd) ; $(LIBTOOL) -dynamic -o ../libsatlas.dylib \
-install_name $(LIBINSTdir)/libsatlas.dylib -current_version $(VER) \
-compatibility_version $(VER) *.o $(LIBS) $(F77SYSLIB)
rm -rf $(tmpd)

So apparently this dylib file is meant for OSX. Why do we need this to be built on Linux? How do I avoid this if this is the case? I didn't touch the PKGBUILD file so this must happen in archlinux as well...

I'm new to package building to please forgive my noobness if this is totally wrong, but any help is appreciated.


peder2tm commented on 2016-05-23 12:08

I had to add -L/usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/ to
to make it compile, i.e. the make targets become: : liblapack.a
ld $(LDFLAGS) -shared -soname -o $@ --whole-archive \
liblapack.a --no-whole-archive $(F77SYSLIB) -L/usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/ -L. -lstcblas -lf77blas -lgcc_s : libptlapack.a
ld $(LDFLAGS) -shared -soname -o $@ --whole-archive \
libptlapack.a --no-whole-archive $(F77SYSLIB) -L/usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/ -L. -lcblas -lblas -lgcc_s

peder2tm commented on 2016-05-21 09:50

I get the following error towards the end of compilation but gcc-libs is installed.

==> Build shared libraries
ld -melf_x86_64 -shared -soname -o --whole-archive libatlas.a \
--no-whole-archive -lc -lpthread -lm
ld -melf_x86_64 -shared -soname -o --whole-archive \
libf77blas.a --no-whole-archive -L/usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib -lgfortran -L. -latlas
ld -melf_x86_64 -shared -soname -o --whole-archive \
libptf77blas.a --no-whole-archive -L/usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib -lgfortran -L. -latlas
ln -s
ld -melf_x86_64 -shared -soname -o --whole-archive \
libcblas.a -L. -latlas -lblas
ld -melf_x86_64 -shared -soname -o --whole-archive \
libptcblas.a -L. -latlas -lblas
ln -s
ld -melf_x86_64 -shared -soname -o --whole-archive \
liblapack.a --no-whole-archive -L/usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib -lgfortran -L. -lstcblas -lf77blas -lgcc_s
ld: cannot find -lgcc
makefile:34: recipe for target '' failed
make: *** [] Error 1
==> ERROR: A failure occurred in build().
==> ERROR: Makepkg was unable to build atlas-lapack.

bartbkr commented on 2016-04-16 17:27

I was finally able to get this working. The reason that the build was failing was that the maximum CPU frequency was being limited by the BIOS. I had to tuhrn off the max CPU freq limit set by the BIOS and ensured that the maximum frequency was that allowed by cpupower, namely 2.401GHZ.


bartbkr commented on 2016-04-10 17:11

Right, I tried to make it clear from my initial post that I've already done what was instructed on that page and the linked SE answer. I am still getting the "CPU Throttling is enabled!" error.

Some output:

$ cat /sys/devices/systemt/cpu/cpu*/cpufreq/scaling_governor

$ cpupower frequency-info
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us
hardware limits: 400 MHz - 2.40 GHz
available frequency steps: 2.40 GHz, 2.40 GHz, 2.30 GHz, 2.10 GHz, 2.00 GHz, 1.80 GHz, 1.70 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.10 GHz, 1000 MHz, 800 MHz, 700 MHz, 500 MHz, 400 MHz
available cpufreq governors: ondemand performance
current policy: frequency should be within 400 MHz and 2.10 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency: 2.10 GHz (asserted by call to hardware)
boost state support:
Supported: yes
Active: yes

morealaz commented on 2016-04-09 16:34

for disabling CPU Throttling.

bartbkr commented on 2016-04-09 14:49

I have Intel Core i5 processor. I've confirmed that now using the acpi_cpufreq driver and intel_pstate=disable on boot. scaling_governor for all four cores is set to performance.

I am still getting the "CPU Throttling is enabled!" error and cannot build. Any suggestions?

greyltc commented on 2016-02-27 12:07

My cpu scaling driver is intel_pstate. By default I'm using the performance governor. Can anyone give me a tip on how to compile this package *without* having to reboot?

giniu commented on 2016-02-25 14:36

@arojas - yes, but provides+conflicts is good anyway in this case I think.

arojas commented on 2016-02-25 12:00

No package should depend on atlas-lapack-base. If some do, it's a bug and should be fixed. Packages should depend on atlas-lapack, atlas-lapack-base is provided as a generic implementation in the repos so that official packages (such as sagemath) can depend on atlas-lapack, but it should be clear that atlas-lapack is the 'right' package to use.

All comments