Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-12-17
Date: Wed, 18 Dec 2013 10:48:12 +0100	[thread overview]
Message-ID: <20131218104812.62edfd68@skate> (raw)
In-Reply-To: <20131218073008.6219E100A64@stock.ovh.net>

Hello,

On Wed, 18 Dec 2013 08:30:08 +0100 (CET), Thomas Petazzoni wrote:

>            python-pycrypto-2.6 | 8 
>               python-pyasn-1.2 | 6 

I have worked on those issues. They are caused by incorrect header and
library paths being passed. The pycrypto header problem is quite easy,
the library path is a little bit trickier, but I'm working on it. I
will be posting patches as soon as possible.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-12-18  9:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2013-12-17 Thomas Petazzoni
2013-12-18  9:48 ` Thomas Petazzoni [this message]
2013-12-18 10:29   ` Peter Korsgaard
2013-12-19  8:36     ` Ryan Barnett

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=20131218104812.62edfd68@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