@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.
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.001683 |
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-libs-snapshotAUR)
- gcc-fortran (gccrs-fortran-gitAUR, gcc11-fortranAUR, gcc-fortran-gitAUR, gcc-fortran-snapshotAUR) (make)
Required by (548)
- 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 528 more...
Sources (4)
mickele commented on 2010-10-19 07:05 (UTC)
<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.
Pinned Comments
phcerdan commented on 2017-06-08 06:48 (UTC) (edited on 2017-06-08 06:49 (UTC) by phcerdan)