Re: Failure (Re: How to use octave-forge?)

[Paul Kienzle]

Neither fink nor darwin ports seem to be providing up to date binaries
for octave+octave-forge which are easy to install on 10.2 and 10.3.

Is this a problem with the fink/ports infrastructure?  Or is it a 
matter of
there being no one doing the wonderful work that Dirk Eddelbuettel
does for Octave+octave-forge in Debian?

If it is a lack of infrastructure, would it be reasonable to put 
together a
binary package like we have for Windows and distribute it from the
octave-forge site?  My inclination is to use the Ports install path, or
possibly opt/loctave.

Any thoughts?

Paul Kienzle
address@hidden

On Dec 23, 2003, at 5:40 PM, Vic Norton wrote:

> Hi Per,
>
> I have downloaded "octave-2.1.50" and configured with
>
>    octave-2.1.50$ ./configure --prefix=/opt/local
>
> However, there is no config.h file in the "octave-2.1.50" directory. 
> The only occurrence of "HAVE_DYLD_API" in the directory is in
>
>    ~/Download/octave-2.1.50/liboctave/oct-shlib.cc
>
> where it appears 3 times.
>
> I see your "#define HAVE_DYLD_API 1" instruction in the 
> "INSTALL.MacOSX" file in the "octave-forge-2003.06.02" distribution. 
> That advice applies to the  "octave-2.1.48" distribution. It's for Mac 
> OSX 10.2.x.
>
> I am running Mac OSX 10.3.2. Maybe the --enable-shared and --enable-dl 
> options will work on this later version of OS X. On the other hand, 
> maybe I need to install octave-2.1.48 so I'll have an config.h file to 
> tweak. Are there any Panther people out there that know the right 
> approach?
>
> This whole thing is a mess. I'm a real Unix novice, and these Mac OS X 
> incompatibilities don't help.
>
> Regards,
>
> Vic
>
> At 10:11 PM +0100 12/23/03, Per Persson wrote:
> > On Dec 23, 2003, at 21:51, Dmitri A. Sergatskov wrote:
> >
> > > Vic Norton wrote:
> > > > Thanks for all the advice about installing octave-forge functions. 
> > > > I am
> > > > sorry to report that my installation efforts have not met with 
> > > > success.
> > > > My octave 2.1.50 has no trouble reading newly installed octave-forge
> > > > m-files, but it cannot execute any oct-files.
> > >
> > > I think for octave-forge to work your octave had to be compiled
> > > with --enable-shared --enable-dl options.
> >
> > No, not on Mac OS X :-(
> >
> > The --enable-shared --enable-dl options won't work on OS X. The 
> > current work-around is to edit config.h _after_ configuring (w/o 
> > --enable-shared --enable-dl options) so that the line: /* #undef 
> > HAVE_DYLD_API */ instead reads: #define HAVE_DYLD_API 1
> >
> > This will (should) let you build and run .oct files.
> >
> > /Per
>
>
>
>
> -------------------------------------------------------------
> Octave is freely available under the terms of the GNU GPL.
>
> Octave's home on the web:  http://www.octave.org
> How to fund new projects:  http://www.octave.org/funding.html
> Subscription information:  http://www.octave.org/archive.html
> -------------------------------------------------------------



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

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------