This section contains a list of problems (and some apparent problems that don't really mean anything is wrong) that may show up during installation of Octave.
infofails to compile if
HAVE_TERMIOS_His defined in config.h. Simply removing the definition from info/config.h should allow it to compile.
dlerror, but not the header file dlfcn.h, you need to find the source for the header file and install it in the directory usr/include. This is reportedly a problem with Slackware 3.1. For Linux/GNU systems, the source for dlfcn.h is in the
You should probably have a shared version of
libstdc++. A patch
is needed to build shared versions of version 2.7.2 of
on the HP-PA architecture. You can find the patch at
libdxmllibrary, resulting in floating point errors and/or segmentation faults in the linear algebra routines called by Octave. If you encounter such problems, then you should modify the configure script so that
SPECIAL_MATH_LIBis not set to
in the kernel configuration files (typically found in the directory /sys/i386/conf. After making this change, you'll need to rebuild the kernel, install it, and reboot.
passing `void (*)()' as argument 2 of `octave_set_signal_handler(int, void (*)(int))'
warning: ANSI C++ prohibits conversion from `(int)' to `(...)'
while compiling sighandlers.cc, you may need to edit some files
gcc include subdirectory to add proper prototypes for
functions there. For example, Ultrix 4.2 needs proper declarations for
signal function and the
SIG_IGN macro in the file
On some systems the
SIG_IGN macro is defined to be something
#define SIG_IGN (void (*)())1
when it should really be something like:
#define SIG_IGN (void (*)(int))1
to match the prototype declaration for the
signal function. This
change should also be made for the
SIG_ERR symbols. It may be necessary to change the
definitions in sys/signal.h as well.
fixproto scripts should
probably fix these problems when
gcc installs its modified set of
header files, but I don't think that's been done yet.
You should not change the files in /usr/include. You
can find the
gcc include directory tree by running the command
The directory of
gcc include files normally begins in the same
directory that contains the file libgcc.a.
zgemm.f: zgemm: warning: unexpected parent of complex expression subtree zgemm.f, line 245: warning: unexpected parent of complex expression subtree warning: unexpected parent of complex expression subtree zgemm.f, line 304: warning: unexpected parent of complex expression subtree warning: unexpected parent of complex expression subtree zgemm.f, line 327: warning: unexpected parent of complex expression subtree pcc_binval: missing IR_CONV in complex op make: *** [zgemm.o] Error 1
when compiling the Fortran subroutines in the libcruft subdirectory, you should either upgrade your compiler or try compiling with optimization turned off.
/usr/tmp/cc007458.s:unknown:Undefined local symbol LBB7656 /usr/tmp/cc007458.s:unknown:Undefined local symbol LBE7656
when compiling Array.cc and Matrix.cc, try recompiling these files without -g.
G_HAVE_SYS_WAITdefined to be 0 instead of 1 when compiling
_tcgetattr _tcsetattr _tcflow
which are part of libposix.a. Unfortunately, linking Octave with -posix results in the following undefined symbols.
.destructors_used .constructors_used _objc_msgSend _NXGetDefaultValue _NXRegisterDefaults .objc_class_name_NXStringTable .objc_class_name_NXBundle
One kluge around this problem is to extract termios.o from libposix.a, put it in Octave's src directory, and add it to the list of files to link together in the makefile. Suggestions for better ways to solve this problem are welcome!
If your system actually does support IEEE arithmetic, you should be able
to fix this problem by modifying the function
the file lo-ieee.cc to correctly initialize Octave's internal
infinity and NaN variables.
If your system does not support IEEE arithmetic but Octave's configure
script incorrectly determined that it does, you can work around the
problem by editing the file config.h to not define
In any case, please report this as a bug since it might be possible to modify Octave's configuration script to automatically determine the proper thing to do.
CPPFLAGS=-I/some/nonstandard/directoryas an argument to
configure. Other variables that can be specified this way are CFLAGS, CXXFLAGS, FFLAGS, and LDFLAGS. Passing them as options to the configure script also records them in the config.status file. By default, CPPFLAGS and LDFLAGS are empty, CFLAGS and CXXFLAGS are set to
"-g -O"and FFLAGS is set to