X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.4 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
MIME-Version:	1.0
In-Reply-To:	<4D8A4CAC.2020106@gmail.com>
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> <4D8A2683 DOT 1010009 AT gmail DOT com> <4D8A2E5F DOT 1040204 AT cwilson DOT fastmail DOT fm> <4D8A32B6 DOT 9050507 AT gmail DOT com> <4D8A472C DOT 7040708 AT cwilson DOT fastmail DOT fm> <4D8A4CAC DOT 2020106 AT gmail DOT com>
Date:	Wed, 23 Mar 2011 20:45:15 +0100
Message-ID:	<AANLkTi=W262n9xjYESZ1g4J0x3wQ9ReyFgUN32ORwwE_@mail.gmail.com>
Subject:	Re: cyggfortran-3.dll broken ?
From:	marco atzeri <marco DOT atzeri AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Cc:	Dave Korn <dave DOT korn DOT cygwin AT gmail DOT com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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 Wed, Mar 23, 2011 at 8:40 PM, Dave Korn  wrote:
> On 23/03/2011 19:17, Charles Wilson wrote:
>> On 3/23/2011 1:49 PM, Dave Korn wrote:
>
>>> =A0 Hmm, I should probably do this. =A0And send it upstream too.
>>
>> Well, yeah (but does upstream want to explicitly require cygwin-1.7.8 or
>> better? or would you conditionalize it on a configure test:
>
> =A0The latter, certainly.
>
> =A0I had a quick try in my 4.3.4-4 build dir; it's a simple matter of add=
ing an
> extra.def file to the linker flags along with a counterbalancing
> '--export-all-symbols' (and since we have a .map file as well this doesn't
> over-export, so I don't need to make a complete .def file, handy!) and I =
could
> conditionalize it on any one of the new HAVE_xxx definitions that are wha=
t's
> causing libgfortan to exclude its own implementations in the new build, s=
o it
> doesn't seem like it should be too hard.
>
> =A0I need to concentrate on fixing LTO for binutils 2.21.1 before I do an=
ything
> else. =A0Apologies to Marco but unless the problem gets worse I'm going b=
ack to
> that and testing the gcc-4.6.0 RC2 for the next few days. =A0I'll try and=
 find
> some background time in which to respin 4.3.4 with forwarders added to th=
e DLL.

the new pc is faster than old one. 2-3 days I should repack all

>
> =A0 =A0cheers,
> =A0 =A0 =A0DaveK
>

Marco

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

- Raw text -