meta-debian and raspberry (linux-base error)

[Valdemar Junior]

hello, anyone.

I am still stuck on generate yocto image from meta-debian.

Every meta package is cloned from morty branch. I run 'bitbake  rpi-basic-image' or 'bitbake core-image-minimal' but its stopped on linux-base do_configure. I read the log but doesnt info the error.

Here is my config files and error log.

conf/local.conf

CPPFLAGS_append_pn-ncurses-native = " -P"
BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}"
PARALLEL_MAKE ?= "-j ${@oe.utils.cpu_count()}"
MACHINE ?= "raspberrypi3"
DISTRO ?= "deby"
PACKAGE_CLASSES ?= "package_deb"
EXTRA_IMAGE_FEATURES = "debug-tweaks"
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
PATCHRESOLVE = "noop"
BB_DISKMON_DIRS = "\
    STOPTASKS,${TMPDIR},1G,100K \
    STOPTASKS,${DL_DIR},1G,100K \
    STOPTASKS,${SSTATE_DIR},1G,100K \
    ABORT,${TMPDIR},100M,1K \
    ABORT,${DL_DIR},100M,1K \
    ABORT,${SSTATE_DIR},100M,1K"
CONF_VERSION = "1"

conf/bblayers.conf

LCONF_VERSION = "6"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
  /usr/src/deby/meta \
  /usr/src/deby/meta-debian \
  /usr/src/deby/meta-debian-extra/meta-jessie-backports \
  /usr/src/deby/meta-debian-extra/meta-stretch \
  /usr/src/deby/meta-raspberrypi \
  /usr/src/deby/meta-openembedded/meta-oe \
  /usr/src/deby/meta-openembedded/meta-python \
  /usr/src/deby/meta-openembedded/meta-perl \
  /usr/src/deby/meta-openembedded/meta-systemd \
  /usr/src/deby/meta-openembedded/meta-gnome \
  "

log.do_configure


DEBUG: Executing python function sysroot_cleansstate
DEBUG: Python function sysroot_cleansstate finished
DEBUG: Executing python function check_oldest_kernel
DEBUG: Python function check_oldest_kernel finished
DEBUG: Executing shell function do_configure
NOTE: LINUX_DEFCONFIG not set, use only .configs in SRC_URI
NOTE: creating the final config with the following .config files:
ERROR: Function failed: do_configure (log file is located at build_rpi/Deby/build/tmp/work/raspberrypi-deby-linux-gnueabi/linux-base/gitAUTOINC+a09e49b41e-r0/temp/log.do_configure.6100)

[HAYASHI Kazuhiro]

Hi,

> /usr/src/deby/meta-raspberrypi \
> /usr/src/deby/meta-openembedded/meta-oe \
> /usr/src/deby/meta-openembedded/meta-python \
> /usr/src/deby/meta-openembedded/meta-perl \
> /usr/src/deby/meta-openembedded/meta-systemd \
> /usr/src/deby/meta-openembedded/meta-gnome \

These foreign layers are incompatible with meta-debian and meta-debian-extra.
They are implemented only for vanilla OE-Core.
meta-debian provides its own recipes for cross-building Debian sources,
so merging them (.bbappend, overriding OE variables, etc.) doesn't work.

https://github.com/meta-debian/meta-debian/tree/morty/bsp/meta-raspberrypi
is a tiny layer for meta-debian to support RaspberryPi 1/2.
Pi 3 is still not supported, which would be done in the near future
by porting several features from meta-raspberrypi.

Regards,
Kazuhiro

On 2017/08/02 1:14, Valdemar Junior wrote:
> hello, anyone.
>
> I am still stuck on generate yocto image from meta-debian.
>
> Every meta package is cloned from morty branch. I run 'bitbake rpi-basic-image' or 'bitbake core-image-minimal' but its stopped on linux-base do_configure. I read the log but doesnt info the error.
>
> Here is my config files and error log.
>
> conf/local.conf
> |

> CPPFLAGS_append_pn-ncurses-native=" -P"

> --
> You received this message because you are subscribed to the Google Groups "DEBY" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to meta-debian...@googlegroups.com <mailto:meta-debian...@googlegroups.com>.
> To post to this group, send email to meta-...@googlegroups.com <mailto:meta-...@googlegroups.com>.
> To view this discussion on the web visit https://groups.google.com/d/msgid/meta-debian/54c352b5-e274-4b1d-a25f-51a0d4f6cc29%40googlegroups.com <https://groups.google.com/d/msgid/meta-debian/54c352b5-e274-4b1d-a25f-51a0d4f6cc29%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

[naveen...@gmail.com]

I'm trying the same thing but even after manually setting LINUX_DEFCONFIG I'm getting the same error.