Hi,Initially, I posted to gsl-discuss about this ... without success. I was about to ask about it on the mingw64 list, but I've just discovered that a dynamic build works fine - so I'll take a punt that this is, after all, a gsl bug and see how I fare here. (I think gsl-discuss might have been the wrong forum anyway.)
I'm trying to build a static gsl-1.14 library with mingw64 in the MSYS shell.
I started with:$ ./configure --build=x86_64-w64-mingw32 --host=x86_64-w64-mingw32 CC=x86_64-w 64-mingw32-gcc CXX=x86_64-w64-mingw32-g++ AR=x86_64-w64-mingw32-ar LD=x86_64-w 64-mingw32-ld NM=x86_64-w64-mingw32-nm RANLIB=x86_64-w64-mingw32-ranlib --dis
able-shared --enable-static && make(For the dynamic build I use the same, except that it's "--disable-static --enable-shared".) Everything is fine until we get near the end of the make process, when this happens:
##########################/bin/sh ./libtool --tag=CC --mode=link x86_64-w64-mingw32-gcc -g -O2 -version-info 15:0:15 -no-undefined -o libgsl.la -rpath /usr/local/lib version.lo block/libgslblock.la blas/libgslblas.la bspline/libgslbspline.la
[SNIP] wavelet/libgslwavelet.la cblas/libgslcblas.la -lmlibtool: link: (cd .libs/libgsl.lax/libgslblock.a && x86_64-w64-mingw32-ar x "/c/_64/comp/gsl-1.14/block/.libs/libgslblock.a") libtool: link: object name conflicts in archive: .libs/libgsl.lax/libgslblock.a//c/_64/comp/gsl-1.14/block/.libs/libgslblock.a
make[2]: *** [libgsl.la] Error 1 make[2]: Leaving directory `/c/_64/comp/gsl-1.14' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/c/_64/comp/gsl-1.14' make: *** [all] Error 2 ########################### A couple of things to note in the above error:Firstly, the 'cd .libs/libgsl.lax/libgslblock.a && x86_64-w64-mingw32-ar x "/c/_64/comp/gsl-1.14/block/.libs/libgslblock.a"' command succeeds. The 3 object files in libgslblock.a are to be found in the .libs/libgsl.lax/libgslblock.a/ folder. Secondly, there are no spaces in the ".libs/libgsl.lax/libgslblock.a//c/_64/comp/gsl-1.14/block/.libs/libgslblock.a" part of the error message - it's presented as one long, continuous (non-existent) path. I also wonder about the double forward slashes ('//c') in there.
Does that error mean anything to anyone here ? Or should I be pursuing it on a mingw64 forum ?
I'm also attaching the configure log and here's my "gcc -v": ################################### r...@desktop2 ~ $ x86_64-w64-mingw32-gcc -v Using built-in specs. Target: x86_64-w64-mingw32Configured with: ../../../build/gcc/gcc/configure --target=x86_64-w64-mingw32 --prefix=/g/buildbot/vista64-mingw32/mingw-x86-x86_64/build/build/root --with-sysroot=/g/buildbot/vista64-mingw32/mingw-x86-x86_64/build/build/root --with-gmp=/g/buildbot/vista64-mingw32/mingw-x86-x86_64/build/build/gmp/install --with-mpfr=/g/buildbot/vista64-mingw32/mingw-x86-x86_64/build/build/mpfr/install --with-mpc=/g/buildbot/vista64-mingw32/mingw-x86-x86_64/build/build/mpc/install --enable-languages=all,obj-c++ --enable-fully-dynamic-string --disable-multilibThread model: win32gcc version 4.4.4 20100208 (prerelease) (GCC)###################################Cheers,Rob
config.log
Description: Binary data
_______________________________________________ Bug-gsl mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gsl
