[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Octave 3.1.51 available for ftp
From: |
John W. Eaton |
Subject: |
Re: Octave 3.1.51 available for ftp |
Date: |
Thu, 24 Jul 2008 09:04:10 -0400 |
On 23-Jul-2008, Thomas Treichl wrote:
| There is one thing that I still don't understand when I compile the sources
and
| maybe someone can give me a hand here: If I try to link liboctave then I get
the
| following error (I know this since building 2.9.12 but I always thought that
| this may be a special problem of my machine?!):
|
| ld: Undefined symbols:
| _fftw_destroy_plan referenced from liboctave expected to be defined in
| /tmp/dependencies-i386/lib/libfftw3.3.dylib
| _fftw_execute_dft referenced from liboctave expected to be defined in
| /tmp/dependencies-i386/lib/libfftw3.3.dylib
| _fftw_execute_dft_r2c referenced from liboctave expected to be defined in
| /tmp/dependencies-i386/lib/libfftw3.3.dylib
| _fftw_import_system_wisdom referenced from liboctave expected to be
defined in
| /tmp/dependencies-i386/lib/libfftw3.3.dylib
| _fftw_plan_many_dft referenced from liboctave expected to be defined in
| /tmp/dependencies-i386/lib/libfftw3.3.dylib
| _fftw_plan_many_dft_r2c referenced from liboctave expected to be defined in
| /tmp/dependencies-i386/lib/libfftw3.3.dylib
| _fftwf_destroy_plan referenced from liboctave expected to be defined in
| /tmp/dependencies-i386/lib/libfftw3f.3.dylib
| _fftwf_execute_dft referenced from liboctave expected to be defined in
| /tmp/dependencies-i386/lib/libfftw3f.3.dylib
| _fftwf_execute_dft_r2c referenced from liboctave expected to be defined in
| /tmp/dependencies-i386/lib/libfftw3f.3.dylib
| _fftwf_import_system_wisdom referenced from liboctave expected to be
defined in
| /tmp/dependencies-i386/lib/libfftw3f.3.dylib
| _fftwf_plan_many_dft referenced from liboctave expected to be defined in
| /tmp/dependencies-i386/lib/libfftw3f.3.dylib
| _fftwf_plan_many_dft_r2c referenced from liboctave expected to be defined
in
| /tmp/dependencies-i386/lib/libfftw3f.3.dylib
| /usr/bin/libtool: internal link edit command failed
| make[2]: *** [liboctinterp.dylib] Error 1
| make[1]: *** [src] Error 2
| make: *** [all] Error 2
| solvedeps-3.1.51.sh: Building Octave.app has failed !!
|
| My workaround for this is to apply a patch of the following form:
|
| --- octave-3.1.51.orig/src/Makefile.in
| +++ octave-3.1.51/src/Makefile.in
|
| OCTINTERP_LINK_DEPS = \
| -L../liboctave $(LIBOCTAVE) -L../libcruft $(LIBCRUFT) $(LIBS) $(FLIBS) \
| - $(OPENGL_LIBS)
| + $(OPENGL_LIBS) $(FFTW_LIBS)
|
| OCT_LINK_DEPS = \
| -L../libcruft $(LIBCRUFT) -L../liboctave $(LIBOCTAVE) \
|
| then I can link liboctave.dylib without any problems left. Any ideas what may
| cause the above problem?
As far as I can tell, fftw functions are only referenced directly in
liboctave, so I don't see why you should need to also link the fftw
library directly with liboctinterp. If this is needed for fftw, why
is it not also needed for the suitesparse libraries?
jwe