Summary: | [science overlay] sci-libs/cholmod-2.0.1: pkg-config fails to find lapack libraries installed from science overlay | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | kaszynek <simonstar> |
Component: | Current packages | Assignee: | Gentoo Science Related Packages <sci> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | nowa |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | about:blank | ||
Package list: | Runtime testing required: | --- |
Description
kaszynek
2012-12-29 19:40:04 UTC
With USE="-supernodal" it builds correctly Same error for sci-libs/arpack-3.1.2 in my case. Which lapack implementation are you using and where does it come from ? Also, don't use pastebins for bugzilla reports. Ok, my fault... It came from science overlay. I didn't noticed that :/ so do you confirm this failure even with lapack from the science overlay? i can't reproduce it here. please post the result of "pkg-config --libs lapack" thanks. The problem with lapack disappeared (I don't know why, it builds correctly even without -supernodal". But same problem with arpack still exists. I've got: [I] virtual/lapack Available versions: 3.0 3.1 (~)3.3[1] {doc} and when I want to emerge arpack: [I] sci-libs/arpack Available versions: 0.96-r3 (~)3.1.2 {doc examples mpi static-libs} Installed versions: 3.1.2(13:38:52 19.10.2012)(examples -doc -mpi -static-libs) i get same error message: configure: error: Cannot find LAPACK libraries pkg-config doesn't find lapack: pkg-config --libs lapack Package lapack was not found in the pkg-config search path. Perhaps you should add the directory containing `lapack.pc' to the PKG_CONFIG_PATH environment variable No package 'lapack' found I meant cholmod in first sentence. Ok, cholmod (with lapack from science overlay) still generates that error in: USE="lapack" emerge -1 cholmod What does "eselect lapack list" says? Available providers for lapack: [1] reference Ok, so I have reemerged lapack-reference and it probably created symlink. Now arpack compiles fine. So, the last version of lapack was same as the new one: Installed versions: 3.4.2[1](22:52:26 20.12.2012)(-static-libs -test -xblas) current: Installed versions: 3.4.2[1](18:37:33 29.01.2013)(-static-libs -test -xblas) But after emerge i have something selected in lapack list: Available providers for lapack: [1] reference * Yes, that's normal. And you shouldn't be able to compile any ebuild depending on lapack if no lapack implementation is eselected first. So as far as I am concerned the behavior was expected as long as nothing was eselected. Same here trying to emerge cholmod-2.1.2 except I have reference lapack eselected. I tried unsetting it and then setting it again but it didn't help. I'm using eselect-1.4-r100 from the sci overlay. Denis. + 03 Feb 2014; Sébastien Fabbro <bicatali@gentoo.org> -cholmod-1.7.4.ebuild, + -cholmod-2.0.1.ebuild, -files/cholmod-1.7.4-debug.patch: + Removed old + if with cholmod-2.1.2 those bugs persist, feel free to re-open > if with cholmod-2.1.2 those bugs persist, feel free to re-open It does, see comment 14. I just reverified it. Denis. With sci-libs/lapack-reference-9999::science # eselect lapack show reference # cholmod-2.1.2 with USE=lapack builds fine for me. [ebuild R ~] sci-libs/cholmod-2.1.2 USE="doc lapack -cuda -metis -minimal -static-libs" 0 KiB The build.log and config.log may give some hints if it still fails. |