Re: Testers needed for an Octave-3.6.1 app (X86_64 only) bundle for MacOS

[Ben Abbott]

*** Tom, please respond at the bottom. Makes it easier for me to follow the 
thread, and for others to catch up ***

On Mar 3, 2012, at 3:00 AM, Thomas Yengst wrote:

> On Mar 2, 2012, at 8:39 PM, Ben Abbott wrote:
> 
>> On Mar 2, 2012, at 11:36 PM, Thomas Yengst <address@hidden> wrote:
>> 
>>> On Mar 2, 2012, at 12:17 PM, Ben Abbott wrote:
>>> 
>>>> On Mar 2, 2012, at 1:35 PM, Thomas Yengst wrote:
>>>> 
>>>>>> From: Ben Abbott <address@hidden>
>>>>>> To: octave maintainers mailing list <address@hidden>
>>>>>> Message-ID: <address@hidden>
>>>>>> Content-Type: text/plain; CHARSET=US-ASCII
>>>>>> 
>>>>>> I've put together a *large* X86_64 app bundle for MacOS X. The DMG is 
>>>>>> about 300MB, and will expand to almost 1GB.
>>>>>> 
>>>>>> Its runs on MacOS 10.7 (Lion) on an i7 based Macbook Pro. It may only 
>>>>>> run on an i7 processor ... and/or only on MacOS 10.7.
>>>>>> 
>>>>>> If anyone is interested in giving it a test-drive, I've started an 
>>>>>> upload to my DropBox. The public link is below.
>>>>>> 
>>>>>> http://dl.dropbox.com/u/14845154/Octave-3.6.1.app.dmg
>>>>>> 
>>>>>> If you give it a try, please let me know if it runs, if plotting works, 
>>>>>> your Mac's processor, and the MacOS version your Mac runs. These last 
>>>>>> two bits of info are available from "About This Mac".
>>>>>> 
>>>>>> Ben
>>>>> 
>>>>> Tested on a Macbook Pro, OS 10.6.8 Snow Leopard with a typical macports 
>>>>> installed.
>>>>> The App clocks in at just under 1 GB, which is basically the same size as 
>>>>> Matlab. Interesting.
>>>>> 
>>>>> It did work - pretty cool. Once you get all the wrinkles ironed out, I 
>>>>> want to know how you did it.
>>>>> I was surprised that it brought up a Mac TERMINAL rather than an xterm or 
>>>>> aquaterm. In addition, got these messages on startup and shutdown
>>>>> 
>>>>> exec '/temp/Octave-3.6.1.app/Contents/MacOS/../Resources/bin/octave'
>>>>> GNU Octave, version 3.6.1
>>>>> Copyright (C) 2012 John W. Eaton and others.
>>>>> This is free software; see the source code for copying conditions.
>>>>> There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or
>>>>> FITNESS FOR A PARTICULAR PURPOSE.  For details, type `warranty'.
>>>>> 
>>>>> Octave was configured for "x86_64-apple-darwin10.8.0".
>>>>> 
>>>>> Additional information about Octave is available at http://www.octave.org.
>>>>> 
>>>>> Please contribute if you find this software useful.
>>>>> For more information, visit http://www.octave.org/help-wanted.html
>>>>> 
>>>>> Read http://www.octave.org/bugs.html to learn how to submit bug reports.
>>>>> 
>>>>> For information about changes from previous versions, type `news'.
>>>>> 
>>>>> error: `lookup' undefined near line 111 column 12
>>>>> error: called from:
>>>>> error:   
>>>>> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/set/ismember.m
>>>>>  at line 111, column 10
>>>>> error:   
>>>>> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/help/unimplemented.m
>>>>>  at line 56, column 5
>>>>> error:   
>>>>> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/set/unique.m
>>>>>  at line 143, column 9
>>>>> error:   
>>>>> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/optimization/__all_opts__.m
>>>>>  at line 56, column 11
>>>>> error:   
>>>>> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/optimization/PKG_ADD
>>>>>  at line 2, column 5
>>>>> octave-3.6.1:1> 
>>>> 
>>>> Thanks for the feedback.  Which cpu does your MacBook Pro have ? (i7, Core 
>>>> Duo, Core 2 Duo, ?)
>>>> 
>>>> The "lookup()" function is included in the bundle. On my MacBook Pro (i7 
>>>> processor) running MacOS 10.7.3 (Lion) ...
>>>> 
>>>> which lookup
>>>> `lookup' is a function from the file 
>>>> /Users/bpabbott/Desktop/Octave-3.6.1.app/Contents/Resources/lib/octave/3.6.1/oct/x86_64-apple-darwin11.3.0/lookup.oct
>>>> 
>>>> What do you get for "which lookup" ?
>>>> 
>>>> What does "PATH" return ?
>>>> 
>>>> To produce the app bundle I used ...
>>>> 
>>>> sudo port mdmg octave36 -fltk
>>>> 
>>>> ... to produce a dmg of everything in /opt/local needed to build and run 
>>>> Octave. I'm using a local Octave36 portfile for this purpose. I then used 
>>>> a Mac with no macports installation to transfer the contents of the dmg 
>>>> stuff into manually constructed app bundle (I have a simple script for 
>>>> that).
>>>> 
>>>> Once all the wrinkles are worked out, I'll document the entire process on 
>>>> the wiki.
>>>> 
>>>> Ben
>>> 
>>> Ben,
>>> 
>>> Macbook Pro with Intel Core 2 Duo
>>> which lookup => nothing, but I can drill down to find it in 
>>> /Octave-3.6.1.app/Contents/Resources/lib/octave/3.6.1/oct/x86_64-apple-darwin11.3.0/lookup.oct
>>> 
>>> my path is:
>>> PATH=/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/local/mysql/bin:/Developer/usr/bin:/Applications/eclipse/AndroidSDK/tools:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
>>> 
>>> it does appear that launching octave.app finds my .octaverc file because 
>>> the first line of output is:
>>> Octave was configured for "x86_64-apple-darwin10.8.0".  <== aka Snow 
>>> Leopard 10.6.8
>>> 
>>> Tom
>> 
>> Tom,
>> 
>> What is the "path" in Octave?
>> 
>> Ben
> 
> Ben,
> 
> Sorry - I misinterpreted your original question. Here is 'path' from the 
> octave prompt:
> 
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/miscellaneous
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/optimization
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/path
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/pkg
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/plot
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/polynomial
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/prefs
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/set
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/signal
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/sparse
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/specfun
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/special-matrix
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/startup
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/statistics
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/statistics/base
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/statistics/distributions
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/statistics/models
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/statistics/tests
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/strings
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/testfun
> /temp/Octave-3.6.1.app/Contents/Resources/share/octave/3.6.1/m/time
> 
> Tom

Opps, my bad, I wanted to check to see if lookup.oct was in the loadpath. 
Unfortunately, I don't see exactly how to do that.

You can check to see of lookup.oct is in your  load path.

        file_in_loadpath lookup.oct

You can also check the exec path.

        strsplit (EXEC_PATH, pathsep)

I get the results below.

 file_in_loadpath lookup.oct
ans = 
/Users/bpabbott/Desktop/Octave-3.6.1.app/Contents/Resources/lib/octave/3.6.1/oct/x86_64-apple-darwin11.3.0/lookup.oct

strsplit (EXEC_PATH, pathsep)
ans = 
{
  [1,1] = 
/Users/bpabbott/Desktop/Octave-3.6.1.app/Contents/Resources/libexec/octave/3.6.1/site/exec/x86_64-apple-darwin11.3.0
  [1,2] = 
/Users/bpabbott/Desktop/Octave-3.6.1.app/Contents/Resources/libexec/octave/api-v48+/site/exec/x86_64-apple-darwin11.3.0
  [1,3] = 
/Users/bpabbott/Desktop/Octave-3.6.1.app/Contents/Resources/libexec/octave/site/exec/x86_64-apple-darwin11.3.0
  [1,4] = 
/Users/bpabbott/Desktop/Octave-3.6.1.app/Contents/Resources/libexec/octave/3.6.1/exec/x86_64-apple-darwin11.3.0
  [1,5] = /Users/bpabbott/Desktop/Octave-3.6.1.app/Contents/Resources/bin
}

As you have an .octaverc file, you should check that there are no contents that 
might break the app bundle by modifying the core loadpath, exec path, or core 
m-file path.

Ben