All of lore.kernel.org
 help / color / mirror / Atom feed
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 10:58:54 +0200	[thread overview]
Message-ID: <20131009105854.6957d8cc@skate> (raw)
In-Reply-To: <CA+csPL6eKEBs3vT4G-Ayx7hUHeZwVvhT85UAsTUWDsmKHWt5LQ@mail.gmail.com>

Dear Espen Frimann Koren,

On Wed, 9 Oct 2013 10:23:49 +0200, Espen Frimann Koren wrote:
> I lost the build log and when I did make clean, it worked :-)
> 
> The link errors did not relate to OpesSSL-libs, but to functions within Qt
> that should have been compiled/present when OpenSSL was enabled. Maybe it
> was a consequence of how I did the build:
> 
> 1. Built all without openssl
> 2. Added openssl and built again, but without clean
> 2.1 Qt is not rebuilt then
> 3. Ran make qt5base-dirclean && make qt5base-build because I needed more
> features in Qt
> 3.1 The link error is present
> 4. make clean && make
> 4.1 Everything builds fine.

Indeed such sequences are not guaranteed to work, but in this specific
case, I'm not sure to understand why it wouldn't work. I'll try to see
if I can reproduce the problem.

Thanks!

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

      reply	other threads:[~2013-10-09  8:58 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
2013-10-09  8:23       ` Espen Frimann Koren
2013-10-09  8:58         ` 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=20131009105854.6957d8cc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.