delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com> |
List-Archive: | <http://sourceware.cygnus.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT sourceware DOT cygnus DOT com> |
List-Help: | <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs> |
Sender: | cygwin-owner AT sourceware DOT cygnus DOT com |
Delivered-To: | mailing list cygwin AT sourceware DOT cygnus DOT com |
Message-ID: | <39636A9C.FB8DD08@lbl.gov> |
Date: | Wed, 05 Jul 2000 10:04:28 -0700 |
From: | Jean-Luc Vay <JLVay AT lbl DOT gov> |
Organization: | Lawrence Berkeley National Laboratory |
X-Mailer: | Mozilla 4.73 [en]C-CCK-MCD LBNL V4.73 Build 1 (WinNT; U) |
X-Accept-Language: | en |
MIME-Version: | 1.0 |
To: | "cygwin AT sourceware DOT cygnus DOT com" <cygwin AT sourceware DOT cygnus DOT com> |
Subject: | linking windows dll with cygwin gcc |
References: | <39611F72 DOT 7D5A4AD0 AT lbl DOT gov> |
I have already sent the following message and got no answer. Am I on the wrong discussion list? I am trying to compile a code running under UNIX on a NT platform. The core subroutine are written in FORTRAN90 with C interfaces to communicate with the language PYTHON. The graphics under PYTHON use the library GIST form the Yorick package. I was able to recompile Yorick and Python using cygwin-gcc and the X11 library. The problems come when I want to link my FORTRAN objects (compiled with Lahey LF95) with the C files compiled with gcc. The FORTRAN objects required some .lib libraries not compatible with gcc and the C objects need some .a libraries incompatible with lf95. I tried to go around that by building .dll libraries. I tried to link c files with gcc importing dll libraries created with lf95 or with BorlandC++ but when I tried the resulting executable, I got the error message "The procedure entry point myprocedure could not be located in the dynamic library mydll.dll". Does someone have an idea of what the problem is or eventually any suggestion of solving the problem in a different way? Jean-Luc -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |