Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: "Bjørn Forsman" <bjorn.forsman@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: SDK confusion!
Date: Tue, 18 Dec 2012 11:06:31 -0600	[thread overview]
Message-ID: <50D0A297.4010702@windriver.com> (raw)
In-Reply-To: <CAEYzJUGy1LR0YomqNEKnYPtVWAtMUpC=R21vZRZAx-SSe8GVVg@mail.gmail.com>

On 12/18/12 7:50 AM, Bjørn Forsman wrote:
> On 17 December 2012 23:20, Mark Hatle <mark.hatle@windriver.com> wrote:
> [...]
>> This is Yocto Project 1.2, the feature arrived sometime between 1.2 and 1.3.
>>
>> The 'danny' branch is 1.3, 'denzil' is 1.2.  I may have said 'denzil' by
>> accident in the last email.
>>
>> Basically you need a newer oe-core to use this feature, or you need to
>> backport it.
>
> Ok. I have switched branches now and got it working for
> core-image-minimal. Thanks.
>
> However, the systemd-image in Angstrom has an issue that breaks
> "bitbake systemd-image -c populate_sdk". I have posted a message on
> their list just now. But basically, the error is this:
>
> $ bitbake systemd-image -c populate_sdk
> [...]
> | Package netbase-dbg (5.0-r1) installed in root is up to date.
> | Collected errors:
> |  * check_conflicts_for: The following packages conflict with openssh:
> |  * check_conflicts_for: 	dropbear *
> |  * opkg_install_cmd: Cannot install package openssh-dev.
> |  * check_conflicts_for: The following packages conflict with openssh:
> |  * check_conflicts_for: 	dropbear *
> |  * opkg_install_cmd: Cannot install package openssh-dbg.

Both dropbear and openssh appear to not be able to be installed at the same time 
due to a stated package conflict.  As to why they are bothy trying to be 
installed, I'm not sure.  Sorry.

--Mark

> | DEBUG: Python function do_populate_sdk finished
> | ERROR: Function failed: populate_sdk_image (see
> /home/bfo/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/beaglebone-angstrom-linux-gnueabi/systemd-image-1.0-r0/temp/log.do_populate_sdk.18052
> for further information)
> ERROR: Task 10 (/home/bfo/setup-scripts/sources/meta-angstrom/recipes-images/angstrom/systemd-image.bb,
> do_populate_sdk) failed with exit code '1'
>
> Best regards,
> Bjørn Forsman
>




  reply	other threads:[~2012-12-18 17:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17 15:31 SDK confusion! Bjørn Forsman
2012-12-17 15:40 ` Mark Hatle
2012-12-17 19:58   ` Bjørn Forsman
2012-12-17 22:11     ` Bjørn Forsman
2012-12-17 22:20       ` Mark Hatle
2012-12-18 13:50         ` Bjørn Forsman
2012-12-18 17:06           ` Mark Hatle [this message]
2012-12-17 22:25   ` Mark Hatle

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=50D0A297.4010702@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=bjorn.forsman@gmail.com \
    --cc=openembedded-core@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