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: <006a01bfe6a9$d9853330$0100000a@TIMYX18EWDT6RQ>
From: "Tim Prince" <tprince AT computer DOT org>
To: "Jean-Luc Vay" <JLVay AT lbl DOT gov>, <cygwin AT sourceware DOT cygnus DOT com>
References: <39611F72 DOT 7D5A4AD0 AT lbl DOT gov> <39636A9C DOT FB8DD08 AT lbl DOT gov>
Subject: Re: linking windows dll with cygwin gcc
Date: Wed, 5 Jul 2000 10:52:54 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.5600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600

As far as the cygwin part is concerned, if anyone could answer this, it
would be here.  I don't believe anyone has tried before to link Lahey
objects under cygwin.  I have obsolete versions of lf90 and lf95 here,
but I haven't looked into anything like this.  lf95 ver 5.0 is the only
one AFAIK where objdump is able to read the .obj files; perhaps that
would be a clue.  I don't have a clue whether Lahey have backed away
intentionally from partial cygwin compatibility.

Tim Prince
----- Original Message -----
From: "Jean-Luc Vay" <JLVay AT lbl DOT gov>
To: <cygwin AT sourceware DOT cygnus DOT com>
Sent: Wednesday, July 05, 2000 10:04 AM
Subject: linking windows dll with cygwin gcc


> 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
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com