From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] qt question
Date: Fri, 13 Jul 2012 00:11:38 +0200 [thread overview]
Message-ID: <20120713001138.5680f85c@skate> (raw)
In-Reply-To: <CALo-6+iNSrRe3um7v5ym6SBwtQtDDrkS2pAbDastOuBdWBbz2w@mail.gmail.com>
Le Wed, 11 Jul 2012 13:33:16 -0700,
Charles Krinke <charles.krinke@gmail.com> a ?crit :
> Well, I had build a complete root file system for this new arm (TI
> AM3517) and booted from it. Then, I got tricky and clicked the button
> for "Qt" and things went downhill from there. So, I guess I am
> searching for where in the buildroot scripts things went awry. I
> believe that since the rest of a modest root file system built, that
> CXX was defined, but maybe not.
Maybe you have enabled C++ support in the toolchain without doing a
complete "make clean && make" cycle.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-07-12 22:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 16:07 [Buildroot] qt question Charles Krinke
2012-07-11 19:40 ` Julian Lunz
2012-07-11 20:33 ` Charles Krinke
2012-07-12 22:11 ` 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=20120713001138.5680f85c@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