[Yocto-builds] ERROR: Nothing PROVIDES 'syslinux'

[r_burton]

On 2013-11-11 15:00, Darren Hart wrote:
> Heh, I thought I was talking to a different r_burton ;-)
> 
> Please don't trim the Cc to a private conversation as now nobody else
> benefits from the time spent answering your question.
> 
> As far as I know, "live" is something specific to x86 - at least in the
> way we build it today. Whether or not a live image is built is
> determined by the IMAGE_FSTYPES which are defined by the BSP/DISTRO you
> are building. To build a live image for an x86 BSP, you typically just
> build the target image:
> 
> $ bitbake core-image-minimal
> 
> That will generate an hddimg (live image) because ia32-base.inc
> includes:
> 
> IMAGE_FSTYPES += "ext3 cpio.gz live"
> 
> Whereas the beagleboard.conf sets:
> 
> IMAGE_FSTYPES += "tar.bz2 jffs2"
> 
> Note the lack of "live". By adding the "live" via Hob, you asked it to
> build something it can't do. Perhaps an IMAGE_FSTYPES_POSSIBLE variable
> could be used to prevent such an error for taking place - but that is a
> question for the Hob developers and the bitbake or oe-core experts 
> (that
> wouldn't be me ;-)
> 
> I'd recommend replying back to the list with the full Cc list so the
> discussion can continue from there.
> 
> Thanks,
> 
> Darren
> 
> 
> 
> On Mon, 2013-11-11 at 13:06 -0500, r_burton wrote:
>> Thank you Darren, I sent to you as well as the rest of the list
>> because I saw that you were the designated maintainer of 'syslinux'.
>> Which the error messages seem to be pointing out.
>> 
>> The short answer: have I built live cross-compiled images for other
>> than x86?  No.
>> 
>> I am trying to build images and apps targeted for a a beagleboard 
>> black
>> (TI ARM 335x).  I am trying to set up the Yocto environment.  When you
>> first take take yocto out of the box and set it off, I think by 
>> default
>> it did build an x86 by default.  It didn't however build a live image.
>> I now have conf/local.conf,  set to MACHINE ?= "beagleboard"
>> 
>> I used 'hob' to select 'live'.  Incidentally, can you tell me the way 
>> to
>> instruct bitbake to build a 'live' image directly, without going 
>> through
>> 'hob'?
>> 
>> Thanks for your kind assistance Darren.
>> Bob
>> 
>> 
>> On 2013-11-11 10:51, Darren Hart wrote:
>> > Have we ever built a live image for anything other then x86?
>> >
>> > On Sun, 2013-11-10 at 20:07 -0500, r_burton wrote:
>> >> I am trying to build a 'live'(e.g.  .img) for core-image-sato-sdk
>> >>
>> >> > bitbake -v core-image-sato-sdk
>> >>
>> >> NOTE: I get the same error regardless of image.
>> >>
>> >> The build fails with this error.
>> >>
>> >> ----------------------------------
>> >> Parsing recipes: 100%
>> >> |###############################################################################| Time: 00:01:03
>> >> Parsing of 857 .bb files complete (0 cached, 857 parsed). 1188
>> >> targets,
>> >> 50 skipped, 0 masked, 0 errors.
>> >> NOTE: Resolving any missing task queue dependencies
>> >> NOTE: selecting pigz-native to satisfy gzip-native due to
>> >> PREFERRED_PROVIDERS
>> >> NOTE: selecting pseudo-native to satisfy virtual/fakeroot-native due
>> >> to
>> >> PREFERRED_PROVIDERS
>> >> NOTE: selecting opkg-native to satisfy opkg-native due to
>> >> PREFERRED_PROVIDERS
>> >> ERROR: Nothing PROVIDES 'syslinux'
>> >> ERROR: syslinux was skipped: incompatible with host
>> >> arm-poky-linux-gnueabi (not in COMPATIBLE_HOST)
>> >> NOTE: Target 'syslinux' is unbuildable, removing...
>> >> Missing or unbuildable dependency chain was: ['syslinux']
>> >> NOTE: Target 'core-image-sato-sdk' is unbuildable, removing...
>> >> Missing or unbuildable dependency chain was: ['core-image-sato-sdk',
>> >> 'syslinux']
>> >> ERROR: Required build target 'core-image-sato-sdk' has no buildable
>> >> providers.
>> >> Missing or unbuildable dependency chain was: ['core-image-sato-sdk',
>> >> 'syslinux']
>> >>
>> >> Any ideas?
>> >> Thanks
>> >> Bob
>> >>