Re: Porting Octave to MacOSX

[A S Hodel]

At 4:32 PM +0100 3/22/01, Per Persson wrote:

>  On torsdag, mars 22, 2001, at 02:45
> , John W. Eaton wrote:
> > 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 autogen.sh 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?
> >
>
> c++ -c  -I. -I.. -I../liboctave
> -I../src -I../libcruft/misc  -I../glob -I../glob -DHAVE_CONFIG_H
> -fno-implicit-templates -g -O2 -Wall toplev.cc -o
> toplev.o
> toplev.cc: In function `class
> octave_value_list Foctave_config_info(const octave_value_list &,
> int)':
> toplev.cc:674: parse error before
> `:'
> toplev.cc:675: parse error before
> `:'
>
> In toplev.cc:674-675
>   m ["UGLY_DEFS"] =
> OCTAVE_CONF_DEFS;
>   m ["UGLY_DEFS"] =
> OCTAVE_CONF_UGLY_DEFS;
>
> from oct-conf.h
> #ifndef OCTAVE_CONF_DEFS
> #define OCTAVE_CONF_DEFS
> "-DOCTAVE_SOURCE=1 -DSEPCHAR=':' -DSEPCHAR_STR=":"
> -DU
> ...
> #ifndef
> OCTAVE_CONF_UGLY_DEFS
> #define OCTAVE_CONF_UGLY_DEFS
> "-DOCTAVE_SOURCE=1 -DSEPCHAR=':' -DSEPCHAR_STR=":"
> -DUSE_READLINE=1 -D__NO\
>
> Its the -DSEPCHAR_STR=":" that
> needs to be changed to -DSEPCHAR_STR=\":\"
> Apparently the same fix is needed for
> MachTen according to the README.MachTen file.
>

I ran into this problem when compiling MachTen; I was unable to get the backslashes to work out right in the MachTen environment, and so my solution

was to simply edit toplev.cc after it was written.

I suspect the culprit here is some problem in the sh interpreter; I recall

trying some experiments that should different behavior using backslashes in

MachTen vs. solaris, compaq alpha, etc.  That is, the problem may be with

the Mac OS X shell.  [I may be displaying my ignorance here...]