[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Some issues with Mac build of octave-2.9.8

From: Joe Koski
Subject: Some issues with Mac build of octave-2.9.8
Date: Thu, 24 Aug 2006 20:37:39 -0600
User-agent: Microsoft-Entourage/

I have successfully built and tested octave-2.9.8, with
octave-forge-2006.07.09. For the most part things are working on my Mac G5
with OS X 10.4.7, Xcode-2.4, g95, and UFsparse-2.0.

Some notes:

When I make check, one test in test_io fails, but it is a different failure
than I encountered previously with 2.9.7, and John fixed. Now

>>>>> processing test_io
  ***** test
 [save_status, save_files] = testls (0);
 [load_status, load_files] = testls (1);
 for f = [save_files, load_files]
   unlink (f{1});
 assert(save_status && load_status);
!!!!! test failed
error: failed: text.mat sparse

There is a text.mat file that was created in the test folder.

For the build I still had to export LIBS=-lcamd before ./configure of octave
to get the build to complete. This is to get some unresolved symbols from
the CAMD library of UFsparse.

Before building, I updated to the latest installer for the Mac gfortran
compiler (July 13, 2006). The result was some unresolved g95 symbols during
the build, so I switched to the g95 compiler (which I prefer, anyway, based
on other experience.) Before the build, I did export LDFLAGS="-lSystemStubs
-lSystem" and everything worked. I may not have needed one or both of those
libraries, but the build went without problems.

I'll check the gfortran list to see if the unresolved symbols problem on a
Mac has been reported. The previous Mac version of gfortran (May 5, 2006)
built octave-2.9.7 without problems.

Let me know if I need to do anything to help resolve the test_io issue.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]