[dss-developer] Trying to build dss11-vm-image

[Bryant Hansen]

Thanks for the fast response, Sergey.

Lukas: If you find yourself desperate enough to dig deep into the 
mechanisms, devshell would probably be the next step.
http://www.openembedded.org/wiki/Devshell

# bitbake -c devshell dss11-vm-image

# cd 
/home/luz/Code/digitalSTROM/dss-oe/angstrom-production-build-eglibc/work/qemux86-angstrom-linux/dss11-image-1.0-r0/

# ./temp/run.do_rootfs.29799

Then you can stop the script immediately when the error occurs and 
possibly edit it to allow it to continue.  This might help to manually 
complete the build process.  To do it automatically likely involves the 
patching of bitbake recipes.

I'm giving this a try myself, but am just on task 854 of 3741.

Cheers,

Bryant

On 09/27/12 12:09, Sergey 'Jin' Bostandzhyan wrote:
> Hi,
>
> On Thu, Sep 27, 2012 at 12:02:37PM +0200, Lukas Zeller wrote:
>> I'm trying to bake the dss11-vm-image target, but it always fails at the very end (do_rootfs) with:
>>
>> ln: failed to create symbolic link `/home/luz/Code/digitalSTROM/dss-oe/angstrom-production-build-eglibc/deploy/images/qemux86/dss11-production-image-1.3.0-qemux86.tar.bz2': File exists
>>
>> which leads to:
>>
>> ERROR: Function 'do_rootfs' failed (see /home/luz/Code/digitalSTROM/dss-oe/angstrom-production-build-eglibc/work/qemux86-angstrom-linux/dss11-image-1.0-r0/temp/log.do_rootfs.29799 for further information)
>>
>>
>> The thing is, that symlink does NOT exist when I look for it after the error occurs, but every time I retry I get the same message again, so it seems it is created in the process and cleaned up afterwards.
>>
>> I tried to re-build a few times with
>>
>>    bitbake -c clean dss11-vm-image
>>    bitbake dss11-vm-image
>>
>> but it always stops with this error.
>
> this is a known problem, since the vm image is not officially supported it
> was kind of a low priority and I did not have time to fix it yet.
>
> You can try to remove /home/luz/Code/digitalSTROM/dss-oe/angstrom-production-build-eglibc/deploy/images/qemux86/dss11-production-image-1.3.0-qemux86.tar.bz2
> and bitbake dss11-vm-image again (without cleaning), in most cases it works
> then.
>
> As an alternative (if you need production), take one of the images here:
> http://feedback.aizo.com/feeds/dss11-production-eglibc/images/qemux86/
>
> And then simply do a regular system update via the web UI in order to get
> the latest version. Again, nothing guaranteed since the VM stuff is
> unofficial and thus untested, but even if you run into some troubles it will
> most likely be possible to fix them on the console.
>
>> Before I dig deep into the mechanisms, I'd like to ask if building dss11-vm-image should just work (I tried in -devel and -production modes) like dss11-image does, or if there are precautions or manual steps to take before building.
>
> I need to change the way how those live images are generated, I think it's
> done differently these times in OE, while I still use an older method.
>
> Kind regards,
> Sergey
>
> _______________________________________________
> dss-developer mailing list
> dss-developer at forum.digitalstrom.org
> http://forum.digitalstrom.org/cgi-bin/mailman/listinfo/dss-developer