Fri 26 Aug 2011 09:20:36 PM UTC, comment #3:
> Mon 22 Aug 2011 03:38:23 AM GMT, comment #2:
> I think the problem with the separator is fixed now, but I don't think it is actually possible to compile a statically linked version of Octave. Is that what you are trying to do? If so, why?
Only because I couldn't get shared libraries to work. However, it turns out that a number of other things were wrong with my environment and the way I was trying to compile stuff that cause various problems with shared libraries, but that all seems to work now. I had my sysadmin update Redhat 5 with the latest rpm's for a lot of stuff.
For example, I ran into a problem (a nice guy with the readline group helped with this) where my LD_LIBRARY_PATH contained several "~/" references, and these were not getting expanded properly. Once I replaced these with full pathnames, and recompiled a lot of stuff, it all began to work. I think this is why Octave was not finding libgfortran.so.3 at one point, for example.
> Mon 22 Aug 2011 03:32:46 AM GMT, comment #1:
> I strongly recommend against compiling with --enable-shared=no and --enable-dl=no. Why did you choose those options?
Out of desperation, because I couldn't figure out anything else. But this is now working.
> I think the missing separator problem is solved by this changeset:
> . . .
> You won't need this changeset at all with 3.4.2 if you don't disable shared libraries and dynamic loading.
I took your advice and this stuff seems to work fine now.
> Why did you need to set the --with-blas and --with-lapack options? Did the configure script not detect them correctly?
I think that the latest Redhat 5 rpm's for them are too old to work with the latest gcc compiler (gcc-4.6.1). To make a long story short, the rpm's contain libgfortran.so.1 whereas the latest software is looking for libgfortran.so.3 . That made anything to do with Fortran not work, which I wrongly interpreted as the Octave installer not being able to find the Fortran libraries at all. So I found out how to install the latest LAPACK and BLAS libraries using ATLAS (atlas3.8.4), which of course meant that I had to point Octave to them. Now it all seems to work fine.
> It might be simpler to add /home/afbacher/GCC/GCC_2_4.6.1/install/bin to your shell PATH before running configure. Then you should be able to skip setting CC, CXX, CPP, and F77 when you run Octave's configure script...
Thanks!
Alan Feuerbacher
|