From: "Sisyphus" <sisyphus1@optusnet.com.au>
To: "Brian Gladman" <brg@gladman.plus.com>,
"gsl-discuss" <gsl-discuss@sourceware.org>
Subject: Re: Building gsl-1.14 with mingw64 in msys shell on MS Windows
Date: Wed, 17 Mar 2010 12:18:00 -0000 [thread overview]
Message-ID: <36F08A02630149AB8441F1C317D53C75@desktop2> (raw)
In-Reply-To: <59E10703DF7A4D8F9E18F344FC025771@BigSlave>
----- 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
prev parent reply other threads:[~2010-03-17 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 12:59 Sisyphus
2010-03-16 14:21 ` Brian Gladman
2010-03-17 12:18 ` Sisyphus [this message]
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=36F08A02630149AB8441F1C317D53C75@desktop2 \
--to=sisyphus1@optusnet.com.au \
--cc=brg@gladman.plus.com \
--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).