octave gives the warning lo_ieee_init warning. this prevents the use of a number of important built-in functions that depend upon ieee floating point bounds. this warning is a result of the configure script being handed what turns out to be a bad option, this was discovered as a result of re-configuring the package manually. after testing the options and flags, the one found problematic was setting the flag LDFLAGS='-lz'. this is in all current octave ebuilds, but was only tested using octave version 2.1.57 Reproducible: Always Steps to Reproduce: 1. run octave from the shell or gui. #> octave 2. use a function that depends upon the initiation of ieee floating point at the prompt. octave-1 > gamma (1) Actual Results: in trying to run the gamma function it produced this error message, ***MESSAGE FROM ROUTINE DGAMLM IN LIBRARY SLATEC. ***FATAL ERROR, PROG ABORTED, TRACEBACK REQUESTED * UNABLE TO FIND XMAX * ERROR NUMBER = 2 * ***END OF MESSAGE ***JOB ABORT DUE TO FATAL ERROR. 0 ERROR MESSAGE SUMMARY LIBRARY SUBROUTINE MESSAGE START NERR LEVEL COUNT SLATEC DGAMLM UNABLE TO FIND XMAX 2 2 1 this is not a problem with slatec. Expected Results: it should have calculated the value of gamma(1) which is 1. Portage 2.0.50-r7 (default-x86-2004.0, gcc-3.3.2, glibc-2.3.2-r9, 2.6.5-gentoo-r1) ================================================================= System uname: 2.6.5-gentoo-r1 i686 AMD Athlon(tm) XP 2600+ Gentoo Base System version 1.4.10 Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=athlon-xp -funroll-loops -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=athlon-xp -funroll-loops -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="ftp://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://www.mirror.ac.uk/sites/www.ibiblio.org/gentoo/ http://gentoo.tiscali.nl/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X acpi alsa apm arts avi berdb berkdb caps cdr cjk crypt cups curl dga doc dvd emacs encode esd fftw flac foomaticdb gdbm gif ginac gmp gnome gpm gstreamer gtk gtk2 guile hdf hdf5 imagemagick imlib java jpeg kde kerberos krb4 lcms leim libg++ libwww mad mikmod mmx motif mozilla mpeg ncurses nls offensive oggvorbis opengl oss pam pdflib perl plotutils png ppds python qt quicktime readline ruby samba sdl slang spell sse ssl svga tcltk tcpd tetex tiff truetype unicode usb wmf x86 xml xml2 xmms xv zlib" octave specific USE flags are "hdf5 mpi" the fix is to remove the LDFLAGS='-lz' from the octave ebuild.
suggested fix does not fully fix the init_ieee_lo problem although it does with a non-ebuild compilation.
Created attachment 32505 [details] ebuild that creates working ieee floating point octave build add "-funroll-loops" to the line containing "filter-flags" in src_compile(). using LDFLAGS='-lk' is still problematic.
Using octave-2.1.57-r1 I get: octave:1> gamma(1) ans = 1 octave:2> Could you recompile with more conservitive CFLAGS?
Nearly a month without reaction - David, still there?
I have I just overlayed the ebuild to include filtering for the -funroll-loops cflag. (As well as removing the LDFLAG) Sorry for the late reply.
WORKSFORME with patches in CVS. David: Please reopen if there are still prolems it didn't see.
