On Wed, Aug 10, 2011 at 10:56 AM, Gordan Bobic <gordan@xxxxxxxxxx> wrote: > On Sat, 06 Aug 2011 10:24:03 +0100, Andrew Haley <aph@xxxxxxxxxx> > wrote: >> On 08/05/2011 09:07 PM, Gordan Bobic wrote: >>> Thanks for pointing out, it does look like the same bug. So what's >>> the >>> fix/workaround? >>> >>> On 08/05/2011 08:59 PM, Niels de Vos wrote: >>>> On 5 Aug 2011 19:15, "Gordan Bobic" <gordan@xxxxxxxxxx >>>> <mailto:gordan@xxxxxxxxxx>> wrote: >>>> > >>>> > 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 >>>> >>>> Looks very much like the error in >>>> https://bugzilla.redhat.com/show_bug.cgi?id=726495 >> >> What is it linking against? __stack_chk_guard should be defined in >> libc.a. > > OK, this is really starting to drive me nuts. I just set up a clean > container from the latest F13 ARM packages, and it looks like glibc > src.rpm from F13 ARM distribution doesn't build either - it fails in the > same place. What magic trick am I missing? How was glibc built > originally? How much memory does your build host have, I seem to remember you need at least a gig, and likely 2gb to build it (although I don't remember exactly), do you have swap enabled? Peter _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
