[MacPorts] #34695: port arpack, update to new atlas library names
#34695: port arpack, update to new atlas library names -------------------------------------+-------------------------------------- Reporter: and.damore@… | Owner: mmoll@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Keywords: | Port: arpack -------------------------------------+-------------------------------------- Atlas changed name to its libraries, it split ''libatlas'' into ''libsatlas'' and ''libmatlas'', cf. ticket:25662#comment:41. Currently port atlas is providing only those two as dylib file while the other libraries are provided as ar archive. 1) port arpack is appending ''liblapack.dylib'' to configure arguments, the configure script fallbacks to ''-llapack'' but there's no need to explictly point a non existing file; 2) an user had missing library reference in his arpack library, I suggest to bump arpack revision to trigger updates, cf. ticket:25662#comment:40 and ticket:25662#comment:56; 3) configure script is setting ''-latlas'', this should be replaced with one of the aforementioned libraries. -- Ticket URL: <https://trac.macports.org/ticket/34695> MacPorts <http://www.macports.org/> Ports system for Mac OS
#34695: port arpack, update to new atlas library names --------------------------------------+------------------------------------- Reporter: and.damore@… | Owner: mmoll@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Resolution: fixed | Keywords: Port: arpack | --------------------------------------+------------------------------------- Changes (by mmoll@…): * status: new => closed * resolution: => fixed Comment: Fixed in r93972. -- Ticket URL: <https://trac.macports.org/ticket/34695#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#34695: port arpack, update to new atlas library names --------------------------------------+------------------------------------- Reporter: and.damore@… | Owner: mmoll@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Resolution: | Keywords: Port: arpack | --------------------------------------+------------------------------------- Changes (by and.damore@…): * status: closed => reopened * resolution: fixed => Comment: Why changing ''liblapack.dylib'' to ''libtatlas.a'' rather than the provided ''liblapack.a''? The latter seems to make more sense since the configure argument is about lapack. Furthermore I was wondering about a conditional patch about the latlas linker flag, configure script (or Makefile after configure phase) needs to use ''-latlas'' when using accelerate because system's library is still libatlas.dylib, and it needs to switch to ''-ltatlas'' when using port atlas. Reopening until further discussion. -- Ticket URL: <https://trac.macports.org/ticket/34695#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#34695: port arpack, update to new atlas library names --------------------------------------+------------------------------------- Reporter: and.damore@… | Owner: mmoll@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Resolution: | Keywords: Port: arpack | --------------------------------------+------------------------------------- Comment(by mmoll@…): Generally speaking, dynamic linking is preferred. The arpack seems to automatically pick up the right atlas location when it is installed, regardless of whether you specify --with-lapack or not. I don't understand the second comment about the conditional patch. Please elaborate on the problem you are seeing. -- Ticket URL: <https://trac.macports.org/ticket/34695#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#34695: port arpack, update to new atlas library names --------------------------------------+------------------------------------- Reporter: and.damore@… | Owner: mmoll@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Resolution: | Keywords: Port: arpack | --------------------------------------+------------------------------------- Comment(by and.damore@…): Replying to [comment:3 mmoll@…]:
Generally speaking, dynamic linking is preferred. The arpack seems to automatically pick up the right atlas location when it is installed, regardless of whether you specify --with-lapack or not.
I didn't realize functions from lapack are exported in the atlas dylibs (I just checked the symbols), I agree that using libtatlas.dylib sounds right.
I don't understand the second comment about the conditional patch. Please elaborate on the problem you are seeing.
When building ''+atlas'', thus passing ''--with- lapack=${prefix}/lib/libtatlas.dylib'' to configure script, there is a reference to -latlas {{{ checking for ATL_xerbla in -latlas... yes }}} That's the system library since port atlas doesn't provide libatlas.dylib. This sounds a wrong behavior, we want to use mp provided atlas when using ''+atlas'' variant. I suggest to manually patch from ''-latlas'' to ''-ltatlas'' after configure phase in ''+atlas'' variant. This is the conditional patch I was talking about. -- Ticket URL: <https://trac.macports.org/ticket/34695#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#34695: port arpack, update to new atlas library names --------------------------------------+------------------------------------- Reporter: and.damore@… | Owner: mmoll@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Resolution: fixed | Keywords: Port: arpack | --------------------------------------+------------------------------------- Changes (by mmoll@…): * status: reopened => closed * resolution: => fixed Comment: Fixed in r94071. -- Ticket URL: <https://trac.macports.org/ticket/34695#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts