From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt 5.0.2 with OpenSSL
Date: Wed, 9 Oct 2013 09:51:54 +0200 [thread overview]
Message-ID: <20131009095154.2d368292@skate> (raw)
In-Reply-To: <CA+csPL5q=rYc_-Q4enRD07Pomj9A6hossAB9cesFnMNnLQv5GA@mail.gmail.com>
Dear Espen Frimann Koren,
(Please keep the Buildroot list in Cc, and avoid top-posting if
possible, thanks!)
On Wed, 9 Oct 2013 09:43:18 +0200, Espen Frimann Koren wrote:
> Nothing that make clean could not fix. Sorry for the "noise".
Ok, but what was the build failure? Probably we can fix it.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-09 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 8:43 [Buildroot] Qt 5.0.2 with OpenSSL Espen Frimann Koren
2013-10-08 8:48 ` Thomas Petazzoni
[not found] ` <CA+csPL5q=rYc_-Q4enRD07Pomj9A6hossAB9cesFnMNnLQv5GA@mail.gmail.com>
2013-10-09 7:51 ` Thomas Petazzoni [this message]
2013-10-09 8:23 ` Espen Frimann Koren
2013-10-09 8:58 ` Thomas Petazzoni
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=20131009095154.2d368292@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