Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-01-08
Date: Thu, 9 Jan 2014 20:14:27 +0100	[thread overview]
Message-ID: <20140109191427.GB3713@free.fr> (raw)
In-Reply-To: <20140109073009.A1897100CCB@stock.ovh.net>

On 2014-01-09 08:30 +0100, Thomas Petazzoni spake thusly:
[--SNIP--]
> Detail of failures
[--SNIP--]
>        arm |                     ola-0.8.32 | NOK | http://autobuild.buildroot.net/results/40a5dde3b553e98c05a7f52d1c1ff7a230686c8b/
>     x86_64 |                     ola-0.8.32 | NOK | http://autobuild.buildroot.net/results/eb94659357e0dc68efd45aaa9e9fa03ee286f533/

OK, so I've digged a bit into that ola build failure.

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).

So, this test is inherently flawed for cross-compilation.

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
  - install a host-google-protobuf as well, so our host Python finds it.

I've tested the first solution, and it builds fine. Not runtime-tested,
since I don't have any OLP hardware.

I'll shortly send a patch with this first solution. If any interested in
this package could test and report sucess/failure, that be great! TIA! ;-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2014-01-09 19:14 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 [this message]
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   ` [Buildroot] [autobuild.buildroot.net] Build results for 2014-01-08 Thomas Petazzoni
2014-01-11 23:17     ` 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=20140109191427.GB3713@free.fr \
    --to=yann.morin.1998@free.fr \
    --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