Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Neuer User <auslands-kv@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: yocto fido: Strange configure error (???)
Date: Mon, 01 Jun 2015 18:28:16 +0200	[thread overview]
Message-ID: <mki170$14s$2@ger.gmane.org> (raw)

Hi

I'm currently moving from Dora to Fido. I moved all my recipes to a new
yocto installation and are modifying the recipes where necessary.

I have a very strange error when configuring a kernel recipe
(linux-cubox-i). Actually, there is no error when using the defaut
recipe included in fido. Only if I add the following bbappend file in
order to change the kernel configuration, I get the error:

FILESEXTRAPATHS_prepend := "${THISDIR}/linux-cubox-i:"

SRC_URI = "file://defconfig \
           file://videoin.cfg \
           file://networking.cfg \
           file://wlan.cfg \
           file://dm-crypt.cfg \
           file://no-caam.cfg \
           file://leds.cfg \
           file://mod-to-builtin.cfg \
           file://watchdog-nowayout.cfg \
"

KERNEL_IMAGETYPE_cubox-i = "zImage"


Error:

| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| WARNING: exit code 128 from a shell command.
| ERROR: Function failed: do_configure (log file is located at
/home/ubuntu/yocto1.8/build/tmp/work/cubox_i-poky-linux-gnueabi/linux-cubox-i/3.14.14-r0/temp/log.do_configure.29043)


Nothing more in the configure log.

Any idea, what is wrong? In general I just want to use a diffent kernel
config. Actually a kernel config that worked before without problems on
dora. I really have no idea, why this isn't working or even what the
error means.

Thanks for any help

Michael



             reply	other threads:[~2015-06-01 16:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01 16:28 Neuer User [this message]
2015-06-01 16:41 ` yocto fido: Strange configure error (???) Gary Thomas
2015-06-01 16:47   ` Neuer User

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='mki170$14s$2@ger.gmane.org' \
    --to=auslands-kv@gmx.de \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox