Changes between Initial Version and Version 1 of Ticket #35195
- Timestamp:
- Jul 14, 2012, 8:53:33 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #35195
- Property Owner changed from macports-tickets@… to tim@…
- Property Cc tim@… removed
-
Property
Summary
changed from
sextractor @2.8.6 Configure error - build failure
tosextractor @2.8.6 Configure error with latest atlas
-
Ticket #35195 – Description
initial v1 1 1 On Mac 10.6.8, Xcode 3.2.6, when executing {{{sudo port upgrade outdated}}} I receive the following: 2 2 3 {{{Error: org.macports.configure for port sextractor returned: configure failure: command execution failed}}} 3 {{{ 4 Error: org.macports.configure for port sextractor returned: configure failure: command execution failed 5 }}} 4 6 5 7 looking at the main.log yields: 6 8 7 {{{:info:configure checking for clapack_dpotrf in -llapack... no 9 {{{ 10 :info:configure checking for clapack_dpotrf in -llapack... no 8 11 :info:configure checking for cblas_dgemm in -lcblas... yes 9 12 :info:configure checking for clapack_dpotrf in -llapack... no 10 13 :info:configure checking for cblas_dgemm in -lcblas... yes 11 :info:configure configure: error: CBLAS/LAPack library files not found in /opt/local/lib! Exiting.}}} 14 :info:configure configure: error: CBLAS/LAPack library files not found in /opt/local/lib! Exiting. 15 }}} 12 16 13 17 so the sextractor configure is bombing. some digging suggests that this is due to the new version of atlas (@3.9.84) which has different library names. According to comments on http://okomestudio.net/biboroku/?p=824 replacing -llapack, -lcblas, -ltpcblas and -latlas in the sextractor configure file with -ltatlas should solve the problem when using recent atlas versions. It is successful if done to the configure script in the 'build/...' directories. I'm not sure how to do this in the portfile