From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Convoluted dependencies
Date: Fri, 07 Oct 2011 09:34:33 -0700 [thread overview]
Message-ID: <4E8F2A19.4030808@linux.intel.com> (raw)
In-Reply-To: <1317996588.2405.18.camel@ted>
On 10/07/2011 07:09 AM, Richard Purdie wrote:
> I've been trying to figure out why our builds take as long as they do.
> It appears our dependency chains are getting more and more convoluted
> and this certainly isn't helping things. Specific pain points look like:
>
> bison-native -> gettext-native
> flex-native -> gettext-native
> (which limits binutils-cross)
>
> gettext-native -> libxml2-native -> python-native
> (hence gettext takes a *long* time to be built)
> What uses the python xml bindings?
>
I thought that by having the --with-included-libxml, we got rid of the
libxml2-native dependency, we should investigate that further.
Digging shows that it is needed for python to create the xml2po tool for
doc translation.
Sau!
> pseudo-native -> sqlite3-native
> (dragging out the time our effectively single threaded init takes)
>
> I'm mentioning this in case anyone has good ideas for fixing some of
> these...
>
> Cheers,
>
> Richard
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2011-10-07 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 14:09 Convoluted dependencies Richard Purdie
2011-10-07 16:34 ` Saul Wold [this message]
2011-10-07 16:54 ` Otavio Salvador
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=4E8F2A19.4030808@linux.intel.com \
--to=sgw@linux.intel.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 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.