From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] dbus-python: select pyexpat dependency
Date: Tue, 19 Nov 2013 00:17:44 +0100 [thread overview]
Message-ID: <20131119001744.7047c794@skate> (raw)
In-Reply-To: <1384814104-11809-1-git-send-email-vsergeev@kumunetworks.com>
Dear Ivan Sergeev,
On Mon, 18 Nov 2013 14:35:03 -0800, Ivan Sergeev wrote:
> dbus-python requires xml.parsers.expat, which is provided by the pyexpat module. This patch enables the pyexpat module when dbus-python is selected.
This looks good, but I don't see the patch in your e-mail :)
> NOTE: I had to delete output/build/python-2.7.3/ for the enabled pyexpat to take effect during a rebuild (simple "make") of buildroot. I presume this is because it's configured and built with python-2.7.3, but perhaps this should be handled automatically -- marking python-2.7.3 "dirty" somehow?
No, Buildroot doesn't try to be smart about detecting what needs to be
rebuilt after a configuration change or a .mk/Config.in change. See
http://buildroot.org/downloads/manual/manual.html#full-rebuild. It's up
to the user to know what to rebuild, or to trigger a full rebuild when
in doubt.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2013-11-18 23:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 22:35 [Buildroot] [PATCH 1/1] dbus-python: select pyexpat dependency Ivan Sergeev
2013-11-18 22:37 ` Ivan Sergeev
2013-11-18 23:32 ` Thomas Petazzoni
2013-11-19 1:55 ` Ivan Sergeev
2013-11-19 2:10 ` Ivan Sergeev
2013-11-30 8:06 ` Peter Korsgaard
2013-11-18 23:17 ` Thomas Petazzoni [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=20131119001744.7047c794@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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