From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29037 invoked by alias); 15 Nov 2011 22:31:37 -0000 Received: (qmail 29027 invoked by uid 22791); 15 Nov 2011 22:31:36 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from imr-db03.mx.aol.com (HELO imr-db03.mx.aol.com) (205.188.91.97) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 15 Nov 2011 22:31:01 +0000 Received: from mtaout-db03.r1000.mx.aol.com (mtaout-db03.r1000.mx.aol.com [172.29.51.195]) by imr-db03.mx.aol.com (8.14.1/8.14.1) with ESMTP id pAFMV0j2006637 for ; Tue, 15 Nov 2011 17:31:00 -0500 Received: from [134.134.139.76] (unknown [134.134.139.76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mtaout-db03.r1000.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id 9DDFBE0000A0 for ; Tue, 15 Nov 2011 17:30:59 -0500 (EST) Message-ID: <4EC2E816.1010806@aol.com> Date: Tue, 15 Nov 2011 22:31:00 -0000 From: Tim Prince Reply-To: tprince@computer.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: shared Libary problems References: <074601cca3dd$e28be2a0$a7a3a7e0$@gov> In-Reply-To: <074601cca3dd$e28be2a0$a7a3a7e0$@gov> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit x-aol-global-disposition: G X-AOL-SCOLL-SCORE: 0:2:356322720:93952408 X-AOL-SCOLL-URL_COUNT: 0 x-aol-sid: 3039ac1d33c34ec2e82310f9 X-AOL-IP: 134.134.139.76 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-11/txt/msg00254.txt.bz2 On 11/15/2011 4:31 PM, Jim Harsh wrote: If you're depending on a specific C++ mangling to match what you've put in your build, bear in mind that no g++ will match any Visual Studio compatible C++ compiler. Normal procedure is to use extern "C" on the C++ side and iso_c_interop on the Fortran side so as to remove mangling on both sides. You may have better chances with the linux build procedure under cygwin, hoping that cygwin g++ may match linux g++. If you normally embed options such as -O2 in your alias for the compiler name when using Intel compilers, you could do the same with gnu compilers. -- Tim Prince -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple