From: Tom Zanussi <tom.zanussi@intel.com>
To: r10kindsofpeople <r10kindsofpeople@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: poky-tiny breaks at ncurses and perl (Dylan 9.0.1)
Date: Fri, 06 Dec 2013 14:08:48 -0600 [thread overview]
Message-ID: <1386360528.3028.62.camel@empanada> (raw)
In-Reply-To: <CAE8H0+XtcT9ZriW31mN28xjDzASAp7AASxOOg=fE9LvepTatRA@mail.gmail.com>
On Fri, 2013-12-06 at 14:08 -0500, r10kindsofpeople wrote:
> After some success building my system (crownbay), I'm now trying to
> optimize boot time, so I read up on poky-tiny, created a new layer and
> am trying to build. I think I've pulled most of my system changes out
> so that I can at least bitbake core-image-minimal, but I'm still not
> able to get past ncurses config and perl. (ncurses reports autoconf
> errors in widec, perl has undefined references to gcvt, I'm also
> getting complaints about multiple providers for the kernel, etc.)
>
>
> Is poky-tiny still active and tested? What are the odds of this being
> resolved in Dora versus the odds of running into other migration
> issues?
>
I haven't tried poky-tiny with dylan, but I have with dora and didn't
run into any build problems - the build errors you're running into
aren't things I've seen either.
So maybe you can try with dora and see what happens - if you still run
into problems, please provide some more details on your setup.
Thanks,
Tom
>
> John
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2013-12-06 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 19:08 poky-tiny breaks at ncurses and perl (Dylan 9.0.1) r10kindsofpeople
2013-12-06 20:08 ` Tom Zanussi [this message]
2013-12-09 19:51 ` r10kindsofpeople
2013-12-09 21:24 ` Saul Wold
2013-12-09 21:45 ` r10kindsofpeople
2013-12-09 22:11 ` Tom Zanussi
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=1386360528.3028.62.camel@empanada \
--to=tom.zanussi@intel.com \
--cc=r10kindsofpeople@gmail.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.