X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-5.4 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_SPAMHAUS_DROP,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By:	sourceware.org
X-Received:	by 10.42.148.71 with SMTP id q7mr30574595icv.53.1362570069260; Wed, 06 Mar 2013 03:41:09 -0800 (PST)
Date:	Wed, 6 Mar 2013 05:41:04 -0600
From:	Yaakov (Cygwin/X) <yselkowitz AT users DOT sourceforge DOT net>
To:	cygwin AT cygwin DOT com
Subject:	Re: Shouldn't gcc-4 depend on libmpfr4 ?
Message-ID:	<20130306054104.4f1a8792@YAAKOV04>
In-Reply-To:	<loom.20130306T120329-190@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
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, 6 Mar 2013 11:08:05 +0000 (UTC), Achim Gratz wrote:
> 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)?

Absolutely NOT.

>  After all, the trigger for the whole exercise was to ensure that gcc
> doesn't pull in two different versions of libmpfr via libmpc1...

Forget the current gcc packages, they're history.  We're about to
upgrade to 4.7 and we anyways need another rebuild before it goes
stable.  If we ship all the updated prereqs now, each built against the
newest gmp, then 4.7.2-2 can be built against them and we won't have
this problem from here on out.


Yaakov

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