Re: [OctDev] octave-forge on solaris 8

[Paul K. <pki...@us...>]

On Jul 1, 2005, at 4:34 PM, Aaron Jackson wrote:

> I hope this is the proper place for this...

Yes.

> I am trying to build octave-forge on a solaris 8 system.  I have never 
> done this before, so I'm not sure what to expect so I have a few 
> questions.  My first question, is that the version of octave I'm using 
> is 2.1.71 while the version of octave-forge is 
> octave-forge-2005.06.13.  Is this a bad idea?  I didn't realize the 
> version mismatch until after I installed 2.1.71 and I would rather not 
> redo the 9+ hour build (octave and octave-forge) if I don't have to.

The octave-forge build skips what can't be built (the -k is done in the 
build).  As far as I'm aware everything in 2005.06.013 should build in 
2.1.71, but I haven't tested this combination.

> Doing a
>
> ./configure --prefix=/opt/sfw
> gmake -k
>
> Seemed to work, but there were a few ld errors along the way.  I guess 
> that's what the -k is for.  However doing a
>
> gmake check
>
> gave me some problems.

>   I did some searching and found that there were some problems with 
> bash specific shell scripts.  The admin/mktests.sh and admin/run_forge 
> scripts do need bash not sh to run.

Are there a lot of changes required for it to run on sh?  I'm happy not 
to depend on bash if it is easy enough.  Please send a patch.

> Also, admin/mktests.sh calls grep -E.  The -E is not a valid switch 
> for /usr/bin/grep for solaris 8.  So either the script needs to call 
> /usr/xpg4/bin/grep, or it needs to call egrep.  After fixing that I 
> was able to run the check.

egrep sounds like a better option.  However, I don't see anything in 
the pattern which requires extended expressions.  Will it work with 
plain grep and no -E option?


>   There were a lot of failed tests and the check eventually errored 
> out (See below.  I can send the fntests.log to anybody who is 
> interested.).  Is this normal, because octave builds and tests very 
> cleanly on this system?

Most tests should work.   From below I suspect that for some reason you 
cannot use compiled functions in oct files.   Does your octave/src 
directory contain *.oct files?  Can you run them from the octave 
command line?

If the answer is no, then try

	./configure --enable-shared --disable-static

and rebuild.  At some point this became the default but I don't 
remember when.  You can also scan through config.log to see if shared 
is enabled if you want to save yourself a nine hour test.

>
> I then did a
>
> gmake install
>
> This also gave me some errors since the install scripts call grep -q.  
> Again, -q is not a valid switch for /usr/bin/grep.

Easy enough to fix these with a >/dev/null.  Might break mingw install 
though.

>
> After fixing that, when I started up octave I got the following errors:
>
>
> error: `dispatch' undefined near line 2 column 1
> error: near line 2 of file 
> `/opt/sfw/share/octave/2.1.71/site/m/octave-forge/comm//PKG_ADD'
> error: source: error sourcing file 
> `/opt/sfw/share/octave/2.1.71/site/m/octave-forge/comm//PKG_ADD'
>
> I then took the advice of the install script and uninstalled 
> octave-forge.  There are some functions in octave-forge that I need 
> access to, but I am having problems installing it.  Has anybody gotten 
> this to work on a solaris 8 machine?  Should I make sure that the 
> versions match and then try everything from scratch?  Thanks for any 
> pointers.

Check the mailing list archives at http://www.octave.org.  There are 
occasional posts Re: Solaris.

- Paul