How does one pick the correct "ports" part of glibc for the correct core? I tried to build the RHEL6 glibc with the F13 ports tar ball, but the build eventually fails: /usr/lib/gcc/armv5tel-redhat-linux-gnueabi/4.4.5/libgcc_eh.a(unwind-arm.o): In function `__gnu_Unwind_Backtrace': (.text+0x8b8): undefined reference to `__stack_chk_guard' collect2: ld returned 1 exit status I'm guessing this is to do with the mismatch between glibc-ports-2.12-26-gcf64098.tar.xz from the F13 package and glibc-2.12-2-gc4ccff1-fedora.tar.bz2 glibc-2.12-2-gc4ccff1.tar.bz2 from the RHEL6 package. Where do I get glibc-ports-2.12-2 ? And what do the 8 characters at the end signify? Gordan On 08/05/2011 01:56 PM, Peter Robinson wrote: > > > On Fri, Aug 5, 2011 at 1:46 PM, Gordan Bobic <gordan@xxxxxxxxxx > <mailto:gordan@xxxxxxxxxx>> wrote: > > On Fri, 5 Aug 2011 13:42:19 +0100, Peter Robinson > <pbrobinson@xxxxxxxxx <mailto:pbrobinson@xxxxxxxxx>> wrote: > > On Fri, Aug 5, 2011 at 1:20 PM, Gordan Bobic wrote: > > Hi, > > > > Are the patches for F13 glibc to make it work on ARM available > > somewhere? I noticed that F13-ARM ships with 2.12-4, but primary > > F13 > > ships with 2.12-1 which was updated to 2.12.2-1. Where are the > > patches > > from 2.12-1 to 2.12-4 for ARM? I found this page: > > > > > http://fedoraproject.org/wiki/Architectures/ARM/Packages_needing_patching > > [2] > > but it only lists F12 packages, the F13 section is empty. > > > > The reason I'm asking is because I'm building RHEL6 for ARM, and > > glibc > > is one off the packages that don't build. Build fails with armv5tel > > not > > supported. I can see in the F13 spec file that the only arm > > specific > > patch applied is tzupdate2.patch, with a couple of ARM specific > > compile > > options and suchlike, I just wanted to make sure there is nothing > > else > > I'm missing. > > > > In the srpm? > > Yes, as I said, I saw the spec file in the srpm, and the only thing I > can see there is the tzupdate2.patch, but that doesn't explain the gap > between 2.12-1 and 2.12-4. My concern is that there may be ARM > specific > fixes between those versions, and primary F13 never appears to have > shipped with 2.12-4. > > > It is basically just that, possibly some changes to the spec file itself > as well from memory when I looked at it. diffing against mainline will > tell you that. The fixes for F-13 weren't accepted upstream, the ones > for F-14 were less bad but I think F-15 will have something that's > acceptable to upstream. > > Peter _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm