Unknown *.al file type on Solaris when linking library using libtool

[Rob Smallshire]

Libtool list,

I am having serious trouble compiling a fourier transform shared library
(http://www.fftw.org) on Solaris which uses libtool for linking. I have
successfully built the shared library on Linux and Irix and I can build it
as a static library on Solaris, but not shared. I have contacted the authors
of the library who can build it on their Solaris setup and a Sourceforge
Solaris machine without issue. I have so far failed with Solaris 8 and
Solaris 9 on independent machines - the latter had a completely fresh
install of *everything* in an attempt to isolate the problem.

I am using the following toolset:

GNU gcc 3.3
GNU ld 2.11.2
GNU make 3.80

The libtool version used by FFTW is 1.43.

The code compiles without problems but the final linking step fails with
errors about unknown file types relating to *.al files.

I configure and make with the following commands:

make distclean
./configure --enable-shared --prefix=/homes/perforce/utils_install/SUN/fftw-
3.0.1-SUN-DEBUG.GCC3
make

The pertinent section of the output is:

/usr/ccs/bin/ld -G -h libfftw3.so.3 -o .libs/libfftw3.so.3.0.1  -z
allextract kernel/.libs/libkernel.al simd/.libs/libsimd.al
dft/.libs/libdft.al dft/codelets/.libs/libdft_codelets.al
dft/codelets/standard/.libs/libdft_standard.al
dft/codelets/inplace/.libs/libdft_inplace.al dft/k7/.libs/libdft_k7.al
dft/k7/codelets/.libs/libdft_codelets_k7.al dft/simd/.libs/libdft_simd.al
dft/simd/codelets/.libs/libdft_codelets_simd.al rdft/.libs/librdft.al
rdft/codelets/.libs/librdft_codelets.al
rdft/codelets/r2hc/.libs/librdft_codelets_r2hc.al
rdft/codelets/hc2r/.libs/librdft_codelets_hc2r.al
rdft/codelets/r2r/.libs/librdft_codelets_r2r.al reodft/.libs/libreodft.al
api/.libs/libapi.al -z defaultextract  -lm -lc
ld: fatal: file simd/.libs/libsimd.al: unknown file type
ld: fatal: file dft/k7/.libs/libdft_k7.al: unknown file type
ld: fatal: file dft/simd/.libs/libdft_simd.al: unknown file type

I don't know what an *.al file - and clearly neither does the linker. I'd be
most grateful of any suggestions that get me moving again on this - its over
a month since I first encountered it.

Thanks in advance,

Rob

Dr Rob Smallshire
Senior Development Engineer
& Structural Geologist
Midland Valley
address@hidden

Download your *free* 4DVista visualizer
now at http://www.mve.com