[Top][All Lists]

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

Porting Octave to MacOSX

From: John W. Eaton
Subject: Porting Octave to MacOSX
Date: Thu, 22 Mar 2001 07:45:01 -0600

On 22-Mar-2001, Per Persson <address@hidden> wrote:

| First the good news: CVS version of Octave compiles nicely under MacOSX 
| (post-beta with the latest set of tools). Replacing config.guess and 
| config.sub and running works smoothly. The only hack needed 
| is replacing ":" with \":\" in oct-conf.h.

Where?  Can you please explain why this is needed?  What error message
did you encounter that prompted the change?

| Bad news: in the final linking stage a number of symbols are undefined 
| (NOT related to link errors in previous versions of OSX). The usual 
| suspect here is a peculiarity with apple's linker where a symbol has to 
| be requested before it is defined, otherwise it will be disposed of.  
| However, I couldn't find any of the missing symbols _anywhere_ which 
| means the problem could be something else.

Did you search .o files?  They are mangled symbol names.  You'll
probably need to use something like

  for f in *.o ; do echo $f ; nm $f | grep get_size__Ct6Array21Zcii ; done

to find them.

| Since I don't have access to a working version of Octave I don't know 
| where these things are supposed to live. Could anybody point me to where 
| the following stuff belongs in Octave's hierarcy?
| /Per
| /usr/bin/ld: Undefined symbols:
| __._t5Array1Z12octave_value
| __._t5Array1Zd
| ...
| ...
| ...

I think most of these symbols should be defined in the files like
Array-C.o that are used to hold the explicit instantiation of template


Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:
How to fund new projects:
Subscription information:

reply via email to

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