From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-01-08
Date: Fri, 10 Jan 2014 07:29:38 +0800 [thread overview]
Message-ID: <20140110072938.27628d13@skate> (raw)
In-Reply-To: <20140109191427.GB3713@free.fr>
Dear Yann E. MORIN,
On Thu, 9 Jan 2014 20:14:27 +0100, Yann E. MORIN wrote:
> What happens is that ola runs the host-python to check if it can
> 'import' the google.protobuf module.
>
> Of course, this fails since google.protobuf is installed in target/ and
> not in host/ (and we do not explicitly install a host-variant).
Correct. But what is odd is that this test was *not* failing before the
migration to the Python infrastructure. I've started investigating
this, but haven't found the reason why before the Python infra it was
building OK, and not after the Python infra.
> There is a very simple trick^Whack we can use to fix this issue, either:
> - remove the test entirely, since we enforce the dependency from the
> Config.in an ola.mk, and thus we know google.protobuf will be
> present
The problem of this solution is that the patch you've done cannot be
upstreamed, and therefore we would have to keep AUTORECONF = YES
forever on this package. Maybe we can make the configure.ac test
conditional on whether we're cross-compiling and push the patch
upstream?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-01-09 23:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-01-08 Thomas Petazzoni
2014-01-09 19:14 ` Yann E. MORIN
2014-01-09 19:15 ` [Buildroot] [PATCH] package/ola: fix build against google.protobuf Yann E. MORIN
2014-01-09 21:05 ` Peter Korsgaard
2014-01-09 23:29 ` Thomas Petazzoni [this message]
2014-01-11 23:17 ` [Buildroot] [autobuild.buildroot.net] Build results for 2014-01-08 Yann E. MORIN
2014-01-14 6:59 ` Arnout Vandecappelle
2014-01-14 20:35 ` Yann E. MORIN
2014-01-26 6:37 ` Thomas Petazzoni
2014-01-26 10:30 ` Yann E. MORIN
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=20140110072938.27628d13@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