Hi, I'm now getting this error on v2013.12-yocto1.5 cloud9-image.bb, while compiling on xubuntu 32-bit 12.04.3. Disk exhaustion is not the cause and I don't think it is memory exhaustion. It may be an internal make error. *Are you compiling on a 32-bit or 64-bit platform?*
I'll investigate further and maybe post the results on the Angstrom list. Other Angstrom images seem to be OK. Regards ... On Thursday, July 18, 2013 5:17:53 PM UTC+10, Dale Schaafsma wrote: > > I crossed my fingers, and resized partitions...got past the disk > exhaustion, and strangely now my disk only has 22G. So somewhere between > the old 30G and the now available 53G was the magic number. > Now unfortunately I'm encountering a build failure with nodejs...google > told me to raise ulimit -s for this...and that didn't work. The build > machine is Debian Wheezy (linux 3.2 if I read things correctly), am I out > of luck with the following? > > ERROR: Function failed: do_compile (see > /home/dales/beagleBoneBlack/angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/temp/log.do_compile.16430 > > for further information) > ERROR: Logfile of failure stored in: > /home/dales/beagleBoneBlack/angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/temp/log.do_compile.16430 > Log data follows: > | DEBUG: Executing shell function do_compile > | make -C out BUILDTYPE=Release V=1 > | make[1]: Entering directory > `/home/dales/beagleBoneBlack/angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out' > | make[1]: execvp: printf: Argument list too long > | make[1]: *** > [/home/dales/beagleBoneBlack/angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out/Release/obj.target/deps/openssl/libopenssl.a] > > Error 127 > | make[1]: Leaving directory > `/home/dales/beagleBoneBlack/angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out' > | make: *** [node] Error 2 > | ERROR: Function failed: do_compile (see > /home/dales/beagleBoneBlack/angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/temp/log.do_compile.16430 > > for further information) > ERROR: Task 861 > (/home/dales/beagleBoneBlack/angstrom/setup-scripts/sources/meta-openembedded/meta-oe/recipes-devtools/nodejs/ > nodejs_0.8.22.bb, do_compile) failed with exit code '1' > NOTE: Tasks Summary: Attempted 6529 tasks of which 6526 didn't need to be > rerun and 1 failed. > Waiting for 0 running tasks to finish: > > > Thanks, > Dale > > On Wednesday, July 17, 2013 3:16:37 PM UTC-5, Dale Schaafsma wrote: >> >> If I might ask...how much disk is taken up by the cloud9-gnome-image >> build? >> The machine I'm using is a little resource constrained and I've filled >> 30+G of disk in my attempt. >> The specific command I'm using is: MACHINE=beaglebone bitbake >> cloud9-gnome-image >> >> Thanks, >> Dale >> ps. FWIW, I was able to build virtual/kernel, but I haven't yet tried the >> resulting kernel, so I may have failed to setup something correctly. >> >> On Wednesday, July 17, 2013 12:53:09 PM UTC-5, chmo...@gmail.com wrote: >>> >>> Hi Martin. >>> >>> I took a look at your post and I can certainly follow it in terms of >>> working with an existing image, but I don't believe that the appropriate >>> images are created by Angstrom, or at least my eyes are failing me and I >>> haven't spotted them. >>> >>> In this case I have a rootfs tarball, a uboot binary, the MLO etc, all >>> of the separate components, and a blank microsd card, which I believe to be >>> what the BBB recipes generate if you follow the instructions in the BB >>> white srm and on the angstrom wiki with MACHINE=beaglebone. >>> >>> I'm trying to figure out how to generate the production programming >>> image, the one on the wiki that boots and programs the production image to >>> the emmc, as well as the bootable image, the one where you can boot the >>> production image directly off of the microsd card. >>> >>> Clearly I can do everything by programming the existing image onto an sd >>> card, mounting it and altering it. That doesn't seem like The Right Thing >>> to do though. >>> >>> Chris >>> >>> >>> On Wednesday, July 17, 2013 11:45:34 AM UTC-4, eskimobob wrote: >>>> >>>> Chris, I'm not entirely sure I am following the main thrust of your >>>> question but I may be able to help with a tiny part. >>>> It is possible to locally mount a disk image and write to it (assuming >>>> sudo) without having to write the image to a card and then mount that. >>>> You >>>> can use "losetup" to create a local loop. >>>> I've included details about that in a blog post about shrinking a disk >>>> image (here<http://www.berriman.co.uk/bbb-mount-and-shrink-a-disk-image> >>>> ). >>>> Hope it help >>>> Martin >>>> >>>> >>>> On Monday, 15 July 2013 21:16:07 UTC+1, chmo...@gmail.com wrote: >>>>> >>>>> Is this close? It would be neat if the image could be made without >>>>> needing a physical card, and sized to the minimum size required but maybe >>>>> it isn't possible to mount and format partitions on a virtual device, >>>>> this >>>>> seems like something Linux should be able to do. >>>>> >>>> -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
