Hi Alexander, Your suggestion worked, thank you!
I just would like to comment that the directions to link LAPACK_LIBS=-L/sw/lib/lapack -lrefblas -lreflapack provided in http://pdb.finkproject.org/pdb/package.php/lapack350?rel_id=10.9-x86_64-current-stable make reference to ‘-lreflapack’, which is absent under /sw/lib/lapack Instead I had to use simply ‘-llapack’, as shown below. If need for future Forum visitors, this is what I did to use lapacke under the FINK installation of lapack350: # Install lapack fink -l install lapack350 (Using ‘-l’ a log file will be saved in /tmp/; if needed you must make a copy of it because such directory gets cleaned after each reboot). # Download and expand lapack-3.5.0.tgz from http://www.netlib.org/lapack/ # Copy the header files to /sw tree sudo su mkdir /sw/include/lapacke/. cp lapack-3.5.0/lapacke/include/*.h /sw/include/lapacke/. # Then, a simple Makefile would look like # ++++++++++++++ HEADERS=-I/sw/include/lapacke LIB_PATH=/sw/lib/lapack LIBRARIES=-L$(LIB_PATH) -lrefblas -llapack -llapacke -lgfortran all: dgels.c /sw/bin/gcc dgels.c -o dgels.x ${HEADERS} ${LIBRARIES} # ++++++++++++++ Where dgels.c is the example provided along the page (as of April 2014) http://www.netlib.org/lapack/lapacke.html ( in my case is the one that starts with /* Calling DGELS using row-major order */ ) Grettings, Temok > If you don't want to wait for a fixed version, the headers are all available > in the lapack-3.5.0.tgz archive. The build procedure doesn't alter them in > any way. Then I would just copy such header files to /sw/include but nonetheless the lapacke.a library files would still be missing, right? On Apr 1, 2014, at 3:39 PM, Alexander Hansen <[email protected]> wrote: > On 4/1/14, 11:51 AM, Cuauhtemoc Salazar wrote: >> Dear FINK users, >> >> I have installed lapack350 on OSX 10.9.2 but I am not able to locate the >> header files corresponding to the C interface to LAPACK, >> lapacke.h (notice the e), >> http://www.netlib.org/lapack/lapacke.html >> in spite of the fact that the installation log file contains lines that >> say it has been compiled: >> ... >> gcc-fsf-4.8 -c -O3 -I ../include -o lapacke_dsyev.o lapacke_dsyev.c >> gcc-fsf-4.8 -c -O3 -I ../include -o lapacke_dsyev_work.o >> lapacke_dsyev_work.c >> gcc-fsf-4.8 -c -O3 -I ../include -o lapacke_dsyevd.o lapacke_dsyevd.c >> … >> >> Also, all these lapacke_XX.o files are absent under /sw, for instance, >> searching for >> find /sw/ -name lapacke_dsyev.o >> or for the header file >> find /sw/ -name lapacke.h >> gives nothing. >> >> In contrast, >> /sw/share/doc/lapack350/lapacke.pdf >> exists. >> >> >> If needed, the header of the log file is: >> Setting runtime build-lock... >> dpkg-deb -b /sw/src/fink.build/root-fink-buildlock-lapack350-3.5.0-1 >> /sw/src/fink.build >> dpkg-deb: building package `fink-buildlock-lapack350-3.5.0-1' in >> `/sw/src/fink.build/fink-buildlock-lapack350-3.5.0-1_2014.03.04-22.02.02_darwin-x86_64.deb'. >> … >> >> Would anyone have any comments on this issue? >> >> Thanks, >> Temok >> >> > > We don't keep .o files around in general. > > The headers are indeed missing--I guess I inadvertently left them out because > the packages that have been using lapack3XY weren't using lapacke. > > If you don't want to wait for a fixed version, the headers are all available > in the lapack-3.5.0.tgz archive. The build procedure doesn't alter them in > any way. > -- > Alexander Hansen, Ph.D. > Fink User Liaison > My package updates: http://finkakh.wordpress.com/
------------------------------------------------------------------------------
_______________________________________________ Fink-beginners mailing list [email protected] List archive: http://news.gmane.org/gmane.os.apple.fink.beginners Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-beginners
