MIME-Version: 1.0
In-Reply-To: <4A288B1C.7010104@gmail.com>
References: <announce.4A189E22.8050002@gmail.com> 	 <4A287EBF.5020408@users.sourceforge.net> 	 <f89dcc3a0906041922w7f95f86bg86cbef9c5ee14940@mail.gmail.com> 	 <4A2886AD.7000602@users.sourceforge.net> <4A288B1C.7010104@gmail.com>
Date: Fri, 5 Jun 2009 14:11:52 +1000
Message-ID: <f89dcc3a0906042111p328e63es486cf50fff1e652a@mail.gmail.com>
Subject: Re: [ANNOUNCEMENT] gmp-4.3.1-1 for cygwin-1.7
From: David Billinghurst <dbcygwin@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Fri, Jun 5, 2009 at 1:03 PM, Dave Korn wrote:
> Yaakov (Cygwin/X) wrote:
>> On 04/06/2009 21:22, David Billinghurst wrote:
>>> As the gmp and mpfr maintainer, can I do anything to fix this?
>>
>> Are you able to reproduce this? =A0I see you built these with gcc4 but
>> with a static libgcc; maybe adding -shared-libgcc would help?
>
> =A0This is the same problem we experienced with file-5.0.whatever-it-was =
just a
> little while ago. =A0There is an old bug in ld thst emits relocs that sho=
uldn't
> be there when compiling a DLL; these relocs then end up getting turned in=
to
> invalid addresses by rebase, which has no reason to believe there's anyth=
ing
> incorrect about them and probably nothing it could do even if it did.
>
> =A0If you build with fresh binutils from CVS head, the created DLL doesn'=
t have
> the problematic reloc. =A0We're rushing out a new binutils release just a=
s soon
> as PR977 can be resolved.

I'll try this tonight.  I have a recent CVS binutils on a machine at home.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/