From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Stefan Seefeld <stefan_seefeld@mentor.com>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-mingw] build error
Date: Thu, 22 May 2014 16:46:31 +0100 [thread overview]
Message-ID: <1400773591.17834.73.camel@ted> (raw)
In-Reply-To: <537DF746.6060700@mentor.com>
On Thu, 2014-05-22 at 09:10 -0400, Stefan Seefeld wrote:
> On 2014-05-22 02:10, Richard Purdie wrote:
> > On Wed, 2014-05-21 at 16:45 -0400, Stefan Seefeld wrote:
> >> Hello,
> >>
> >> I started experimenting with the meta-mingw layer today, using the
> >> 'daisy' branch for both, poky as well as meta-mingw.
> >>
> >> Running `bitbake meta-toolchain`, the build process failed in one of the
> >> last steps (1003 of 1005) with:
> >>
> >> ERROR: nativesdk-packagegroup-sdk-host not found in the base feeds
> >> (x86_64-nativesdk-mingw32 noarch any all).
> >>
> >> Any idea what I may be missing ? I'm using
> >>
> >> MACHINE ??= "qemux86"
> >> SDKMACHINE ?= "x86_64-mingw32"
> >
> > Which pacxkage backend were you using? If you didn't use ipk, I'd
> > suggest trying it. In theory others should work but its ipk I've been
> > using when working with those layers.
>
> OK, I was using rpm (the default), but now switched to ipk. That results
> in a different error in meta/lib/oe/sdk.py:55, where do_populate() tries
> to link ld.so.cache into a non-existent directory.
> I have attempted a fix with the attached patch.
I think this was fixed on master, there is a patch we need to backport
to daisy. I've just done that since I've been aware of that issue.
> With that, things now appear to be working. (I think things should also
> work with 'rpm' as package backend, though, right ? Should I file a bug
> report somewhere to put that on record ?)
You can file a bug in the bugzilla for it, yes.
Cheers,
Richard
prev parent reply other threads:[~2014-05-22 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 20:45 [meta-mingw] build error Stefan Seefeld
2014-05-22 6:10 ` Richard Purdie
2014-05-22 13:10 ` Stefan Seefeld
2014-05-22 15:46 ` Richard Purdie [this message]
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=1400773591.17834.73.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=stefan_seefeld@mentor.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.