From: "Sisyphus" <sisyphus1@optusnet.com.au>
To: "gsl-discuss" <gsl-discuss@sourceware.org>
Subject: Building gsl-1.14 with mingw64 in msys shell on MS Windows
Date: Tue, 16 Mar 2010 12:59:00 -0000 [thread overview]
Message-ID: <9011A67E67854955A42C43918D16EB9E@desktop2> (raw)
Hi,
I have Windows Vista64, and I was trying to build gsl-1.14 in the msys shell
using mingw64 (gcc-4.4.4).
I started with:
$
./configure --build=x86_64-w64-mingw32 --host=x86_64-w64-mingw32 --disable-shared
--enable-static && make
It ran for quite a long time - I was even starting to think it was going to
succeed. Eventually the 'make' step croaked with:
make[2]: Entering directory `/c/_64/comp/gsl-1.14'
/bin/sh ./libtool --tag=CC --mode=compile
x86_64-w64-mingw32-gcc -DHAVE_CONFIG_H -I. -g -O2 -MT
version.lo -MD -MP -MF .deps/version.Tpo -c -o version.lo version.c
libtool: compile: x86_64-w64-mingw32-gcc -DHAVE_CONFIG_H -I. -g -O2 -MT
version.lo -MD -MP -MF .deps/version.Tpo -c version.c -o version.o
mv -f .deps/version.Tpo .deps/version.Plo
/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 complex/libgslcomplex.la
cheb/libgslcheb.la dht/libgsldht.la diff/libgsldiff.la deriv/libgslderiv.la
eigen/libgsleigen.la err/libgslerr.la fft/libgslfft.la fit/libgslfit.la
histogram/libgslhistogram.la ieee-utils/libgslieeeutils.la
integration/libgslintegration.la interpolation/libgslinterpolation.la
linalg/libgsllinalg.la matrix/libgslmatrix.la min/libgslmin.la
monte/libgslmonte.la multifit/libgslmultifit.la multimin/libgslmultimin.la
multiroots/libgslmultiroots.la ntuple/libgslntuple.la
ode-initval/libgslodeiv.la permutation/libgslpermutation.la
combination/libgslcombination.la multiset/libgslmultiset.la
poly/libgslpoly.la qrng/libgslqrng.la randist/libgslrandist.la
rng/libgslrng.la roots/libgslroots.la siman/libgslsiman.la
sort/libgslsort.la specfunc/libgslspecfunc.la statistics/libgslstatistics.la
sum/libgslsum.la sys/libgslsys.la test/libgsltest.la utils/libutils.la
vector/libgslvector.la cdf/libgslcdf.la wavelet/libgslwavelet.la
cblas/libgslcblas.la -lm
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
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
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.
Cheers,
Rob
next reply other threads:[~2010-03-16 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 12:59 Sisyphus [this message]
2010-03-16 14:21 ` Brian Gladman
2010-03-17 12:18 ` Sisyphus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9011A67E67854955A42C43918D16EB9E@desktop2 \
--to=sisyphus1@optusnet.com.au \
--cc=gsl-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).