[MacPorts] #34695: port arpack, update to new atlas library names

[MacPorts]

#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