Re: oemake problems

Would I be able to get around this problem if I try using the pre-built tool chain? Thanks and Regards, Ravi. On Fri, 27 Aug 2004 Ravi Nandiraju wrote : >Hi, > I tried killing the build and tried to rebuild gpe-image again but every time the build comes upto this stage and remains there endlessly. There are no obvious errors(at least for me) that show up. Any pointers for debugging this particular issue??? > >Thanks and Regards, >Ravi. > ><snip> >NOTE: package bison-native: build completed >NOTE: package binutils-cross: build started >NOTE: package binutils-cross-2.15.91.0.1-r0: task do_fetch started >NOTE: package binutils-cross-2.15.91.0.1-r0: task do_fetch completed >NOTE: package binutils-cross-2.15.91.0.1-r0: task do_build started >NOTE: package binutils-cross-2.15.91.0.1-r0: task do_build completed >NOTE: package binutils-cross: build completed >NOTE: package gcc-cross-initial: build started >NOTE: package gcc-cross-initial-3.3.4-r0: task do_fetch started >NOTE: package gcc-cross-initial-3.3.4-r0: task do_fetch completed >NOTE: package gcc-cross-initial-3.3.4-r0: task do_build started >NOTE: package gcc-cross-initial-3.3.4-r0: task do_build completed >NOTE: package gcc-cross-initial: build completed >NOTE: package linux-libc-headers: build started >NOTE: package linux-libc-headers-2.6.7.0-r2: task do_fetch started >NOTE: package linux-libc-headers-2.6.7.0-r2: task do_fetch completed >NOTE: package linux-libc-headers-2.6.7.0-r2: task do_build started >NOTE: package linux-libc-headers-2.6.7.0-r2: task do_build completed >NOTE: package linux-libc-headers: build completed >NOTE: package glibc: build started >NOTE: package glibc-2.3.2+cvs20040726-r8: task do_fetch started >NOTE: package glibc-2.3.2+cvs20040726-r8: task do_fetch completed >NOTE: package glibc-2.3.2+cvs20040726-r8: task do_package started > > > > > >On Mon, 23 Aug 2004 Joshua Wise wrote : > >>256MB RAM is a little on the low side -- to ensure a comfortable OE > >>experience, you really want at least 512MB. But, even so, I wouldn't > >>expect glibc to take anything like 14 hours to build on your machine. I > >>suggest you check the logfiles to see where it got stuck. > > > >When building at full optimizations on my system (for any platform!), I've seen GCC occasionally sit for awhile doing apparently nothing (although sucking down full CPU cycles). My voodoo response after 15 minutes on the same file or so is to kill gcc and run make again. This may do the trick for you, or it might not. > > > >(I wonder if it's time to memtest86 again...) > > > >joshua > >_______________________________________________ >H2200-port mailing list >H2200-port.a.t.handhelds.org >https://handhelds.org/mailman/listinfo/h2200-port
Received on Fri Aug 27 09:30:27 2004