Re: Problems after building octave-forge-2.1.73 on Mac OS X

[Joe Koski]

on 3/27/06 2:54 PM, Martin Costabel at address@hidden wrote:

> Joe Koski wrote:
>> After building octave-2.1.73 on my Mac, with the usual
>> 
>>   export LDFLAGS='-L/usr/lib -lcc_dynamic'
>>   ./configure --enable-shared --disable-static
>>   make
>>   sudo make install
>> 
>> I got the normal octave opening statements (without any errors reported) and
>> the normal octave prompt. This was with OS X 10.3.9, Xcode Tools 1.5, and
>> g77-3.4.4. All seemed OK. This is the same configuration that successfully
>> built octave-2.1.72 and, recently, octave-forge-2006.03.17.
>> 
>> Then I built octave-forge-2006.03.17 for octave-2.1.73 with the usual
>> ./configure, make, sudo make install sequence. This finished without any
>> major errors reported. Upon opening octave, I get
>> 
>> Report bugs to <address@hidden> (but first, please read
>> http://www.octave.org/bugs.html to learn how to write a helpful report).
>> 
>> error: `dispatch' undefined near line 2 column 1
>> error: near line 2 of file
>> `/usr/local/share/octave/2.1.73/site/m/octave-forge/comm//PKG_ADD'
>> error: source: error sourcing file
>> `/usr/local/share/octave/2.1.73/site/m/octave-forge/comm//PKG_ADD'
> 
> This is a problem with loading bundles. Octave's libdl mechanism doesn't
> work on MacOSX, and unfortunately the mechanism that does work, dyld, is
> disabled in 2.1.73 due to a bug in configure. This is a botched bug fix
> from 2.1.72.
> 
> In 2.1.72, configure looked for a header <Mach-O/dyld.h> which worked on
> a non-case-sensitive file system, that is, for the majority of Mac
> users. On a case-sensitive file system it did not work, because the
> file's real name is <mach-o/dyld.h>. I reported this bug, and it was
> fixed. Unfortunately, at the same time the variable
> ac_cv_header_Mach_O_dyld_h was renamed to ac_cv_header_mach_o_dyld_h,
> but not everywhere.
> 
> If you change configure line 17315
> 
>    if test "$ac_cv_header_Mach_O_dyld_h" = yes; then
> 
> to
> 
>    if test "$ac_cv_header_mach_o_dyld_h" = yes; then
> 
> and rebuild octave, chances are that your error will go away.

Martin,

Your change to the configure script did indeed solve the problem. My
octave-2.1.73 and octave-forge-2006-03-17 are now functioning properly.

Many thanks.

Joe




-------------------------------------------------------------
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
-------------------------------------------------------------