help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Can't install octave-forge packages in a 32-bit OS X build, but can in a


From: Alexander Hansen
Subject: Can't install octave-forge packages in a 32-bit OS X build, but can in a 64-bit one
Date: Fri, 04 Nov 2011 21:03:18 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1

Hi.  I'm the maintainer for Octave for the Fink project,  serving Mac
OS X.

One of our users reported a problem in Octave-3.4.3, built as 32-bit,
on Mac OS 10.6.8, which I confirmed, wherein 'pkg' was unable to
install anything, e.g :

octave:1> pkg -verbose install physicalconstants-0.1.7.tar.gz
mkdir (/var/tmp/oct-2rjbOh)
untar (physicalconstants-0.1.7.tar.gz, /var/tmp/oct-2rjbOh)
invalid assignment to cs-list outside multiple assignment
error: called from `dir' in file
/sw32/share/octave/3.4.3/m/miscellaneous/dir.m near line 115, column 26
error: called from:
error:   /sw32/share/octave/3.4.3/m/pkg/pkg.m at line 832, column 5
error:   /sw32/share/octave/3.4.3/m/pkg/pkg.m at line 361, column 9

I've tried removing some semicolons to see if I can debug where this
goes awry, but it appears to be simply the assignment on line 115 of
dir.m:

          info(i,1).name = fn;


In contrast, a 64-bit build on the same machine works properly.  The
two builds use the same C and C++ compilers:

octave:4> octave_config_info('CC_VERSION')
ans = 4.2.1 (Apple Inc. build 5666) (dot 3)
octave:5> octave_config_info('CXX_VERSION')
ans = 4.2.1

(Xcode tools 3.2.6) but different Fortran compilers:  a 32-bit
gfortran and a 64-bit gfortran, respectively, for the 32-bit and
64-bit Octave.

Apart from the expected differences I'd naively expect from 32 vs. 64
bits, I also saw a few other things.  The 64-bit build's configuration
had:

checking for working mktime... no

vs. "yes" on the 32-bit one.  Also, the 64-bit build had

checking for working nanosleep... no (mishandles large arguments)

whereas the 32-bit one had "yes".  Only the 32-bit build was given the
-mieee-fp modifier ("flag-sort -r" is a Perl script that we use that
changes the ordering of arguments to the compiler--it was needed in
this case because of a conflict with another package):

checking whether flag-sort -r gcc accepts -mieee-fp... yes
configure: adding -mieee-fp to XTRA_CFLAGS
checking whether flag-sort -r g++ accepts -mieee-fp... yes
configure: adding -mieee-fp to XTRA_CXXFLAGS
...
checking whether /sw32/bin/gfortran-fsf-4.6 accepts -mieee-fp... yes
adding -mieee-fp to FFLAGS
configure: defining FFLAGS to be -O3 -mieee-fp


In the build output, the only thing that seemed to be different
between the two cases was the presence of the -mieee-fp flag.

I'm stumped here, so I'd appreciate any suggestions, and I'll gladly
provide any additional information.
-- 
Alexander Hansen, Ph.D.
Fink User Liaison
http://finkakh.wordpress.com/


reply via email to

[Prev in Thread] Current Thread [Next in Thread]