Instead of performing the bitbake of all recipes at once why don’t you try doing the bitbake of every recipe in a separate process? For example if you plan to use postfix, do a bitbake postfix. This is to make sure which recipes of a certain release is the one giving problems. If this doesn’t work and the daisy and dizzy recipes don’t work well together in a single image, I’d suggest you to contact yocto https://www.yoctoproject.org/about . They may be able to give you a more detailed suggestion.
i dont understand how bitbake postfix alone should solve the problems i have?
the result are errors because a class cant be found which is available within poky dizzy but not poky daisy...
to replace poky daisy from intels sdk with poky dizzy produces also errors like for example the watchdog-samples...
i dont think yocto is the right place to ask about problems with intels yocto implementation...
if i use openembedded with intels poky daisy does not work and if i use intels sdk with poky dizzy does not work too!
how can i unmark the question as answered?
To unmark a question as answered you need to mark some other reply in the thread as correct answer and then unmark it as correct. This will leave the status as not answered.
thx that worked
back to the yocto troubles...
endless troubles with the yocto nonsense
understand the users who are no longer use that and change to debian
POOR documentation, senseless complicated, too many steps to have a working system
such a great board and such a stupid decision to bother users with yocto
its no longer important