From: Saul Wold <sgw@linux.intel.com>
To: r10kindsofpeople <r10kindsofpeople@gmail.com>,
Tom Zanussi <tom.zanussi@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: poky-tiny breaks at ncurses and perl (Dylan 9.0.1)
Date: Mon, 09 Dec 2013 13:24:15 -0800 [thread overview]
Message-ID: <52A634FF.8020705@linux.intel.com> (raw)
In-Reply-To: <CAE8H0+U_XmpsS=iVrGbWp6um6nMUXxDb+fighV7KruBuFRGWFw@mail.gmail.com>
On 12/09/2013 11:51 AM, r10kindsofpeople wrote:
> On Fri, Dec 6, 2013 at 3:08 PM, Tom Zanussi <tom.zanussi@intel.com
> <mailto:tom.zanussi@intel.com>> wrote:
>
> 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...using Dora, I was able to get the basic system to build.
>
> Adding some features (dhcp-server, for instance) still breaks the build,
> but I suspect that's just a consequence of -tiny doing it's thing.
>
John, that's probably correct, the tiny configuration uses uclibc and if
you see bug number 5431
(https://bugzilla.yoctoproject.org/show_bug.cgi?id=5431), there are a
number of recipes that will not build correctly with the full uclibc,
but that was with a full uclibc, where as the tiny configuration cuts
down ulibc to just support the bare minimum.
Hope that helps with your efforts.
Sau!
> John
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
next prev parent reply other threads:[~2013-12-09 21:24 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
2013-12-09 19:51 ` r10kindsofpeople
2013-12-09 21:24 ` Saul Wold [this message]
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=52A634FF.8020705@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=r10kindsofpeople@gmail.com \
--cc=tom.zanussi@intel.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.