Comments on: Building LAPACK and Ruby’s linalg on Mac OS X

By: How do I install ruby linalg library on Mac? - Quora

How do I install ruby linalg library on Mac? - Quora — Fri, 02 Dec 2011 07:47:36 +0000

[...] stories going back to 2008 and it looks like there was a patch in plans but it never came to life: http://www.commonmediainc.com/20... and here http://www.pauldix.net/2008/06/i…http://rubyforge.org/forum/forum…Regardless of these [...]

By: John Burgoon

John Burgoon — Wed, 18 Mar 2009 21:59:15 +0000

Thanks so much for this page. I followed the advice from #10 above for Mac Leopard and it ran like a charm. The TIMER = INT_CPU_TIME setting worked for me, too.

One note: In my case, I ran the script as shown to edit the make.inc, then manually edited the make.inc to say “gfortran” instead of “g77″. THEN I commented out the sed stuff in the script (so it wouldn’t overwrite my changes) and then ran the script again.

By: James M. Lawrence

James M. Lawrence — Sun, 07 Sep 2008 14:51:41 +0000

These issues should be fixed in the new release, which I have gratuitously called 1.0.0.

After I applied Luis Parravicini’s patch to use g2c, then replaced all ‘.so’ instances with CONFIG["DLEXT"], it worked immediately. I installed g77 from http://hpc.sourceforge.net .

There is a new Mac binary available for the new release http://rubyforge.org/frs/?group_id=273

Thanks to all who provided help during my extended hiatus.

By: Joseph Wilk

Joseph Wilk — Thu, 04 Sep 2008 09:37:37 +0000

This worked for me on Leopard 10.5.4, Ruby 1.8.7,
gfortran: 4.3.0, lapack-3.1.1.

I had to follow Rob Rambos advice and run
“sudo ln -s /sw/include/f2c.h /usr/local/include/”

I also had to manually copy over the linalg.bundle and lapack.bundle from my linalg build to my ruby site_ruby folder (/local/lib/ruby/site_ruby/1.8/i686-darwin9).

I found it useful to run the linalg extconf.rb files directly for lapack and linalg to find out why things where not working:

cd ext/lapack/; ruby extconf.rb
cd ext/linalg/; ruby extconf.rb

By: James Kyle

James Kyle — Sat, 23 Aug 2008 15:37:00 +0000

To fix the ld errors for etime, edit the make.inc @ approx line 29.

Comment out TIMER = EXT_ETIME

Uncomment TIMER = INT_CPU_TIME

This worked for me on Leopard 10.5.4, macports gcc43′s gfortran-mp, lapack-3.1.1.

Cheers,

James

By: Dimitris

Dimitris — Fri, 01 Aug 2008 14:39:26 +0000

Tim, Darrell,

I found that this helps (on OSX 10.4.11):

change lines 22 & 23 in dsecnd_EXT_ETIME.f and second_EXT_ETIME.f to
REAL EXT_ETIME
EXTERNAL EXT_ETIME

Found here: http://www.pauldix.net/2008/06/installing-lina.html

By: Rob Rambo

Rob Rambo — Fri, 04 Jul 2008 23:46:46 +0000

Thanks for the posting. I had some issues with f2c.h not being found. I am running OS X 10.5.2 and the f2c.h header is in /sw/include. Creating the following link fixed the problem.

sudo ln -s /sw/include/f2c.h /usr/local/include/

By: Darrell Swenson

Darrell Swenson — Wed, 18 Jun 2008 18:14:31 +0000

I had the same problem as TIm. I found the following link helpful.

http://gcc.gnu.org/ml/fortran/2007-02/msg00400.html

In my case the two files that needed editing were second_EXT_ETIME.f and dsecnd_EXT_ETIME.f

By: David Bean

David Bean — Sat, 03 May 2008 09:10:01 +0000

Ooops…one more hack I had to make:

My ruby install needed those .so dynamic libs to be named as .bundle. (!) Then I had to hack my linalg.rb file to look like this:

require ‘universal-darwin8.0/lapack.bundle’
require ‘universal-darwin8.0/linalg.bundle’

Now I fire up IRB and do ‘require ‘linalg” => true

whew,,,

By: pjmorse

pjmorse — Wed, 23 Apr 2008 13:09:25 +0000

Tim, which Fortran compiler are you using? The errors you’re getting are missing files in the INSTALL subdirectory of the LAPACK distribution, which should be built early in the makefile. My make.log shows lines like

g77 -o testsecond second_EXT_ETIME.o secondtst.o

…so if g77 (or whatever is masquerading as g77 on your system) isn’t working properly, those won’t get built, and when the makefile tries anything depending on them, it will fail.