From: Julian Lunz <git@jlunz.de>
To: buildroot@busybox.net
Subject: [Buildroot] Qt tribulations take 2
Date: Sat, 14 Jul 2012 18:25:55 +0200 [thread overview]
Message-ID: <20120714182555.4b7b267d@jl-desk-LL> (raw)
In-Reply-To: <CALo-6+gv+zb1peT7ngOGLL7VnS6xpCUOZRn_J6CD86Kmn7vX=A@mail.gmail.com>
Took your provided config and gave it a try on my machine (32bit-Ubuntu
10.04).
Went through without any hassles :/
What's your environment?
On Fri, 13 Jul 2012 08:41:37 -0700
Charles Krinke <charles.krinke@gmail.com> wrote:
> My apologies, Thomas, I did mean buildroot-2012.05 and here is its
> .config renamed as dotconfig. In the mean time, I am frustrating
> myself with !#$%* openembedded in an attempt to glean some knowledge
> about how Qt fits together in an embedded environment as I slide into
> this new project.
>
> Charles
>
> On Fri, Jul 13, 2012 at 7:55 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> > Le Fri, 13 Jul 2012 06:51:34 -0700,
> > Charles Krinke <charles.krinke@gmail.com> a ?crit :
> >
> >> Let me start over with my Qt question.
> >>
> >> I downloaded buildroot-2011.05 and ran several tests, each with
> >> "make
> >
> > I presume you wanted to say 2012.05, right?
> >
> >> clean && make" and each with C++ support checked, both with powerpc
> >> and arm and the results are the same, so either my understanding of
> >> what to click in xconfig is faulty (probable) or there is an issue
> >> in the Qt package scripts. In both cases, I can compile
> >> successfully without Qt checked and in both cases, I get into
> >> problems with Qt checked. I would have expected one of powerpc or
> >> arm to successfully compile and wonder if a suggestion could be
> >> made. Creating qmake. Please wait...
> >> make[1]: Entering directory
> >> `/home/ckrinke/buildroot-2012.05/output/build/qt-4.8.1/qmake'
> >> make[1]: c: Command not found
> >> make[1]: [project.o] Error 127 (ignored)
> >> make[1]: c: Command not found
> >> make[1]: [property.o] Error 127 (ignored)
> >
> > Please send your Buildroot .config file.
> >
> > Thanks!
> >
> > Thomas
> > --
> > Thomas Petazzoni, Free Electrons
> > Kernel, drivers, real-time and embedded Linux
> > development, consulting, training and support.
> > http://free-electrons.com
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot
>
>
>
next prev parent reply other threads:[~2012-07-14 16:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 13:51 [Buildroot] Qt tribulations take 2 Charles Krinke
2012-07-13 14:55 ` Thomas Petazzoni
2012-07-13 15:41 ` Charles Krinke
2012-07-14 16:25 ` Julian Lunz [this message]
2012-07-14 22:00 ` Charles Krinke
2012-07-14 23:05 ` Thomas Petazzoni
2012-07-15 10:33 ` Arnout Vandecappelle
2012-07-15 10:38 ` Thomas Petazzoni
2012-08-16 17:28 ` Stephan Hoffmann
2012-08-17 11:29 ` Thomas Petazzoni
2012-07-14 23:12 ` Arnout Vandecappelle
2012-07-14 20:56 ` Arnout Vandecappelle
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=20120714182555.4b7b267d@jl-desk-LL \
--to=git@jlunz.de \
--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.