X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.2 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_BG,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
Message-ID: <4D8A2683.1010009@gmail.com>
Date: Wed, 23 Mar 2011 16:57:39 +0000
From: Dave Korn <dave DOT korn DOT cygwin AT gmail DOT com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: cyggfortran-3.dll broken ?
References: <AANLkTi=WaAY1HY2bZ2zKHHuCkpNE4oLCZ8cY1J=CV1Ma AT mail DOT gmail DOT com>	<4D8A1775 DOT 5020601 AT gmail DOT com>	<4D8A1BCD DOT 2080506 AT gmail DOT com> <AANLkTinGfQi2ad4yTbDydrzbURQATtTT4zVJWG01V5LS AT mail DOT gmail DOT com> <4D8A214D DOT 6090409 AT cwilson DOT fastmail DOT fm>
In-Reply-To: <4D8A214D.6090409@cwilson.fastmail.fm>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

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