From: Dave Korn <dave.korn.cygwin@gmail.com>
To: cygwin@cygwin.com
Subject: Re: cyggfortran-3.dll broken ?
Date: Wed, 23 Mar 2011 17:15:00 -0000 [thread overview]
Message-ID: <4D8A2683.1010009@gmail.com> (raw)
In-Reply-To: <4D8A214D.6090409@cwilson.fastmail.fm>
On 23/03/2011 16:35, Charles Wilson wrote:
> I think it would just take a few statements in a .def file like
>
> carg = CYGWIN1.carg
> cargf = CYGWIN1.cargf
> ccos = CYGWIN1.ccos
>
> but I'm not sure...
Yes, that's basically it (or equivalent in a .directve section), but,
indeed, as you point out:
> And, of course, the process of building gcc runtime libraries is a
> bit...opaque...so "adding blah to a .def file" may be harder than it
> sounds.
Nah, it's only libtool and autoconf, nothing to be scared of!
> And if you DO it this way, I'm pretty sure ld will go ahead and
> create import entries in the .dll.a for them.
Yes, that's what we'd want to happen isn't it? The import stub imports the
symbol from libgfortran, the runtime loader finds it in libgfortran and
performs the forwarding, everything Just Works. No?
> Or is it simply time to bump the DLL number for cygwin's gfortran runtime?
Urgh. Don't want to diverge our DLL numbers from upstream if at all possible.
cheers,
DaveK
--
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
next prev parent reply other threads:[~2011-03-23 16:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 15:07 marco atzeri
2011-03-23 16:12 ` Dave Korn
2011-03-23 16:19 ` Dave Korn
2011-03-23 16:19 ` marco atzeri
2011-03-23 16:35 ` Dave Korn
2011-03-23 16:37 ` marco atzeri
2011-03-23 17:29 ` Don Ward
2011-03-23 18:44 ` marco atzeri
2011-03-23 16:38 ` Corinna Vinschen
2011-03-23 16:58 ` Dave Korn
2011-03-23 16:36 ` Charles Wilson
2011-03-23 17:15 ` Dave Korn [this message]
2011-03-23 17:35 ` Charles Wilson
2011-03-23 17:51 ` Dave Korn
[not found] ` <COL102-W3605F958314136F1E27881B5B70@phx.gbl>
2011-03-23 18:27 ` FW: " Karl M
2011-03-23 18:39 ` Fw: " Dave Korn
2011-03-23 19:41 ` Charles Wilson
2011-03-23 19:45 ` Dave Korn
2011-03-23 19:50 ` marco atzeri
2011-03-29 1:31 Daniel Jensen
2011-03-29 13:46 ` Dave Korn
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=4D8A2683.1010009@gmail.com \
--to=dave.korn.cygwin@gmail.com \
--cc=cygwin@cygwin.com \
/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).