On Sat, Aug 29, 2009 at 12:23 AM, Alex Lancaster<al...@users.sourceforge.net> wrote:
> which produces the error: > > warning: lo_ieee_init: unrecognized floating point format! > warning: autoload: `./__java__.oct' is not an absolute file name > warning: autoload: `./__java__.oct' is not an absolute file name > warning: autoload: `./__java__.oct' is not an absolute file name > warning: autoload: `./__java__.oct' is not an absolute file name > warning: autoload: `./__java__.oct' is not an absolute file name > warning: autoload: `./__java__.oct' is not an absolute file name > warning: autoload: `./__java__.oct' is not an absolute file name > warning: autoload: `./__java__.oct' is not an absolute file name > warning: autoload: `./__java__.oct' is not an absolute file name > warning: autoload: `./__java__.oct' is not an absolute file name > mkdir (/tmp/oct-Me8WmG) > untar (/var/tmp/java-1.2.6.tar.gz, /tmp/oct-Me8WmG) > error: memory exhausted or requested size too large for range of Octave's > index type -- eval failed > > I'm not sure how to debug much further than this. > I can reproduce this error on FC11 (i386) with octave 3.2.2 as well. I did few steps futher: try to install java package from the octave prompt: octave:1> pkg install java-1.2.6.tar.gz warning: lo_ieee_init: unrecognized floating point format! warning: lo_ieee_init: unrecognized floating point format! warning: lo_ieee_init: unrecognized floating point format! __java__.cc: In function ‘void initialize_jvm()’: __java__.cc:385: warning: deprecated conversion from string constant to ‘char*’ ... < few warnings deleted > ... 2 problems (2 warnings)error: memory exhausted or requested size too large for range of Octave's index type -- trying to return to prompt octave:1> Then I tried to build the package in bash shell with ./configure and make, then it succeeds: 2 problems (2 warnings)rm -f octave.jar jar cf octave.jar org/octave/ClassHelper.class org/octave/OctClassLoader.class org/octave/Octave.class org/octave/OctaveReference.class org/octave/Matrix.class It appears to me that it is this "jar cf ... " command that crashes octave's pkg. So may be it is an octave bug. Crossposting to the octave mailing list... > More details available on the Fedora downstream bug: > > https://bugzilla.redhat.com/show_bug.cgi?id=510841 > > Note that ppc, ppc64 and x86_64 builds all seem to complete correctly. > > Alex > > Dmitri. -- ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
