From: Tim Prince <n8tm@aol.com>
To: cygwin@cygwin.com
Subject: Re: shared Libary problems
Date: Tue, 15 Nov 2011 22:31:00 -0000 [thread overview]
Message-ID: <4EC2E816.1010806@aol.com> (raw)
In-Reply-To: <074601cca3dd$e28be2a0$a7a3a7e0$@gov>
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
prev parent reply other threads:[~2011-11-15 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 21:31 Jim Harsh
2011-11-15 21:52 ` René Berber
2011-11-15 21:59 ` Charles Wilson
2011-11-15 22:31 ` Tim Prince [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=4EC2E816.1010806@aol.com \
--to=n8tm@aol.com \
--cc=cygwin@cygwin.com \
--cc=tprince@computer.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).