Re: gmp issue resolution

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This problem actually sounds familiar like with the F15 or F17 build. Not sure if it was the same package or not.

What is the next "blocker" if this is considered resolved? 


Is there any followup on our part for making sure our list of fixes are getting pushed upstream? Ie there are peeps willing to do -easy- stuff, and just double-checking list to make sure the patches are getting applied upstream, and maybe even back to the original source actually sounds helpful. It is tedious, and time consuming but it isn't terribly hard if you have an accurate list and a patch in hand.

It is a pain maintaining the list, but it makes is super easy for people to jump in and help when they have spare cycles.

I'm not implying this is the problem in this particular case, but if say this was found before, and the fix never made it upstream back
through the process. It might only be a 5 minute human time fix, but it also wasted maybe 15-20 minutes of builder time, and more importantly it might stop the entire build process which in turn backs up the release date.

It is actually important. And it should free up some time for a few people.



From: Peter Robinson <pbrobinson@xxxxxxxxx>
To: Jon Masters <jcm@xxxxxxxxxx>
Cc: "arm@xxxxxxxxxxxxxxxxxxxxxxx" <arm@xxxxxxxxxxxxxxxxxxxxxxx>
Sent: Friday, January 4, 2013 6:43 AM
Subject: Re: gmp issue resolution

On Fri, Jan 4, 2013 at 11:19 AM, Jon Masters <jcm@xxxxxxxxxx> wrote:
> On 01/04/2013 03:30 AM, Peter Robinson wrote:
>> On Fri, Jan 4, 2013 at 3:39 AM, Jon Masters <jcm@xxxxxxxxxx> wrote:
>>> Hi Peter,
>>>
>>> So the issue we have been experiencing with gmp is actually binutils
>>> related. There is a known regression in binutils wherein certain
>>> assembly is not recognized as ARM if it contains extraneous space!
>>>
>>> http://lists.gnu.org/archive/html/bug-binutils/2012-11/msg00104.html
>>>
>>> I'm copying Nick Clifton, because he'll want to make sure that
>>> ultimately we get the fix into binutils in F19/rawhide. But in the
>>> interim, you can go ahead and apply the following tested patch to gmp
>>> that just removes the extraneous space in udiv.asm for ARM. Once
>>> binutils is fixed, this patch is obviated and harmless.
>>
>> We'll need the fix in F-18 too then as they both contain the same
>> release of binutils. Upstream BZ is
>> http://sourceware.org/bugzilla/show_bug.cgi?id=14887 Nick do you want
>> a RHBZ too?
>
> Great. Meanwhile, I expect my gmp patch will apply as-is to F18 also if
> you want to go and apply that. It's the same 5.0.5 release of gmp.

It's not causing us issues as yet so I think I'll await a proper
binutils fix for f18.

Peter
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/arm

_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/arm

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux ARM (Vger)]     [Linux ARM]     [ARM Kernel]     [Fedora User Discussion]     [Older Fedora Users Discussion]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Maintainers]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

Powered by Linux