X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-0.9 required=5.0 tests=AWL,BAYES_00,FSL_HELO_BARE_IP_2,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Achim Gratz <Stromeko AT NexGo DOT DE>
Subject:	Re: Shouldn't gcc-4 depend on libmpfr4 ?
Date:	Wed, 6 Mar 2013 11:57:51 +0000 (UTC)
Lines:	16
Message-ID:	<loom.20130306T125459-574@post.gmane.org>
References:	<CAEhDDbDwsH=CvsJXFFTgbrEhVp_-sUU-q-=tJONYaKP=m95Weg AT mail DOT gmail DOT com> <5131CD7E DOT 8050001 AT gmail DOT com> <loom DOT 20130304T080048-222 AT post DOT gmane DOT org> <20130304090904 DOT GA5468 AT calimero DOT vinschen DOT de> <loom DOT 20130304T110538-61 AT post DOT gmane DOT org> <20130304161925 DOT GA4078 AT calimero DOT vinschen DOT de> <loom DOT 20130304T193416-681 AT post DOT gmane DOT org> <CA+sc5mk2MgnjYA2OtaK7d7Aed_tpqXVoD=80NVQ6-uO=LNSUpw AT mail DOT gmail DOT com> <87ip57nf3r DOT fsf AT Rainer DOT invalid> <20130305034127 DOT 22dc8a65 AT YAAKOV04> <loom DOT 20130305T115614-775 AT post DOT gmane DOT org> <20130306033005 DOT 411192a5 AT YAAKOV04> <loom DOT 20130306T120329-190 AT post DOT gmane DOT org>
Mime-Version:	1.0
User-Agent:	Loom/3.14 (http://gmane.org/)
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

Achim Gratz <Stromeko <at> NexGo.DE> writes:
> I've produced a 5.0.5 package anyway so that library will be at the latest
> existing version just to be sure.  Now, the remaining problem is that updating
> libmpc produces cygmpc-3.dll while gcc expects cygmpc-1.dll.  Should these be
> linked (the ABI is AFAICT the same since the original cygmpc-1.dll was produced
> by overriding the version number)?  After all, the trigger for the whole
> exercise was to ensure that gcc doesn't pull in two different versions of
> libmpfr via libmpc1...

Gcc now links to cyggmp-3.dll and cyggmp-10.dll and it doesn't like that a bit.
 Here the ABI is different, so a symbolic link won't work.


Regards,
Achim.



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