From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6512 invoked by alias); 17 Mar 2010 12:18:42 -0000 Received: (qmail 6500 invoked by uid 22791); 17 Mar 2010 12:18:41 -0000 X-SWARE-Spam-Status: No, hits=-0.5 required=5.0 tests=AWL,BAYES_50 X-Spam-Check-By: sourceware.org Received: from mail05.syd.optusnet.com.au (HELO mail05.syd.optusnet.com.au) (211.29.132.186) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 17 Mar 2010 12:18:37 +0000 Received: from desktop2 ([203.202.164.190]) (authenticated sender sisyphus1) by mail05.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id o2HCIIUe009407; Wed, 17 Mar 2010 23:18:26 +1100 Message-ID: <36F08A02630149AB8441F1C317D53C75@desktop2> From: "Sisyphus" To: "Brian Gladman" , "gsl-discuss" References: <9011A67E67854955A42C43918D16EB9E@desktop2> <59E10703DF7A4D8F9E18F344FC025771@BigSlave> In-Reply-To: <59E10703DF7A4D8F9E18F344FC025771@BigSlave> Subject: Re: Building gsl-1.14 with mingw64 in msys shell on MS Windows Date: Wed, 17 Mar 2010 12:18:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit Mailing-List: contact gsl-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gsl-discuss-owner@sourceware.org X-SW-Source: 2010-q1/txt/msg00061.txt.bz2 ----- Original Message ----- From: "Brian Gladman" >> 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