Re: [yocto] unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

Robert, since I think you implemented this, any idea what might be going wrong here? Cheers, Paul On Tuesday 26 November 2013 17:27:30 Todd Stellanova wrote: > Tried creating a fresh build folder and giving the vm more ram but the > results are basically the same: > > Allocated inode: 15264 > c

[yocto] Weekly Build Available

The weekly build is about the be available at: http://autobuilder.yoctoproject.org/pub/nightly/20131127-1 Please begin scheduled testing. bitbake 347b2ead091f00ee60703f6f3d17cfdd9075ac07 eclipse-poky-juno e8342d27db60a9d1b627ddb9f8ae2f5512bfc0c9 eclipse-poky-kepler

Re: [yocto] Errors with update-rc.d: /etc/init.d/XXX exists during rc.d purge (use -f to force)

Hi Paul, good to hear I'm not the only one suffering from this issue... No, I've received no response on the mailing list yet, but maybe someone has a hint for us now? The only "workaround" I found is to purge the package and afterwards install the new version. I know this is a really dirty work

Re: [yocto] Errors with update-rc.d: /etc/init.d/XXX exists during rc.d purge (use -f to force)

Richard -- My "workaround" was a little less drastic than yours. (grin) Before upgrading to the new package via 'dpkg -i', I would edit the postrm script in /var/lib/dpkg/info/,postrm, adding the "-f" argument to "force" the symlink removal, as suggested by the error message. Then the upgrade

Re: [yocto] Weekly Build Available

> > http://autobuilder.yoctoproject.org/pub/nightly/20131127-1 > > Please begin scheduled testing. > > bitbake 347b2ead091f00ee60703f6f3d17cfdd9075ac07 > eclipse-poky-juno e8342d27db60a9d1b627ddb9f8ae2f5512bfc0c9 > eclipse-poky-kepler 3dd620d9f89e297ee9e22d5

Re: [yocto] FW: Weekly Build Available

Folks, We're respinning right now. The new build will be available in a few hours at: http://autobuilder.yoctoproject.org/pub/nightly/20131127-3 bitbake 347b2ead091f00ee60703f6f3d17cfdd9075ac07 eclipse-poky-juno e8342d27db60a9d1b627ddb9f8ae2f5512bfc0c9 eclipse-poky-k

[yocto] How to use pre-built external Yocto toolchain

I must be missing something obvious. It's easy for me to build and install a toolchain package using bitbake meta-toolchain The resulting toolchain package shows up at... ./tmp/deploy/sdk/poky-eglibc-i686-meta-toolchain-core2-toolchain-1.5.sh ...which is easy to install. It seems the proper way t

Re: [yocto] FW: Weekly Build Available

Hi Beth, I can not access 20131127-3 directory because it doesn't exist. There is only 20131127-4 directory Would you please confirm it ? Thanks, Yi 于 2013年11月28日 01:32, Flanagan, Elizabeth 写道: Folks, We're respinning right now. The new build will be available in a few hours

Re: [yocto] unbootable image produced with PACKAGE_CLASSES ?= "package_ipk", /etc missing

Hi Paul, Thanks, seems not enough space when ipk ? I will try a ipk build today. // Robert On 11/27/2013 06:57 PM, Paul Eggleton wrote: Robert, since I think you implemented this, any idea what might be going wrong here? Cheers, Paul On Tuesday 26 November 2013 17:27:30 Todd Stellanova wrot

[yocto] Patch failure with bbappends

Hi All, I am seeing an interesting effect due to a specific commit to bitbake/poky, which is causing the patching of gcc-* recipes from the meta-xilinx layer to fail. I understand that master of oe-core has switched to using GCC 4.8.2 since dora, however no changes to microblaze were added bet