This is the mail archive of the
gsl-discuss@sourceware.org
mailing list for the GSL project.
Re: Building gsl-1.14 with mingw64 in msys shell on MS Windows
----- Original Message -----
From: "Brian Gladman" <brg@gladman.plus.com>
libtool: link: (cd .libs/libgsl.lax/libgslblock.a && 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
Does anyone here know what's required to get it to build successfully on
this platform ? I can build a 32-bit library on the same PC, but I'd
really like to have a 64-bit build if such is possible. Unfortunately,
the error message doesn't mean anything to me.
Not with mingw64. But I provide a 64-bit build of GSL-1.14 using Visual
Studio 2010 here:
http://gladman.plushost.co.uk/oldsite/computing/gsl-1.14-vc10.zip
Thanks, Brian - for the moment, my interest is in having gsl build
successfully with mingw64 in the MSYS shell.
It's probably not apparent in the post I sent but, in the actual output to
the console, there's no space between ".libs/libgsl.lax/libgslblock.a" and
"//c/_64/comp/gsl-1.14/block/.libs/libgslblock.a" in the error message -
which strikes me as odd. And why are there *two* adjacent forward slashes in
there ?
It's also odd that the preceding 'cd .libs/libgsl.lax/libgslblock.a && ar x
"/c/_64/comp/gsl-1.14/block/.libs/libgslblock.a"' command has succeeded -
and I can manually cd to .libs/libgsl.lax/libgslblock.a and run 'ar x
"/c/_64/comp/gsl-1.14/block/.libs/libgslblock.a"' without any problems (and
no warnings being emitted).
If there's no further response here by tomorrow morning I'll see if the guys
on the mingw64 mailing list have any ideas as to what's going wrong. So
near, and yet so far ...
Cheers,
Rob