From: Ormund Williams <ormundw@panix.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt fails to build
Date: Wed, 02 Dec 2009 18:44:14 -0500 [thread overview]
Message-ID: <1259797454.1750.34.camel@station1.ormlab.com> (raw)
In-Reply-To: <87ocn3y40l.fsf@macbook.be.48ers.dk>
On Sun, 2009-11-15 at 20:36 +0100, Peter Korsgaard wrote:
> >>>>> "Ormund" == Ormund Williams <ormundw@panix.com> writes:
>
> Ormund> Hi All,
> Ormund> I did a git pull this morning and now I get this error, no change to
> Ormund> the .config file:
>
> Ormund> Creating qmake. Please wait...
> Ormund> make[1]: Entering directory .../buildroot/output/build/qt-embedded-linux-opensource-src-4.5.2/qmake'
> Ormund> g++: @: No such file or directory
> Ormund> make[1]: *** [project.o] Error 1
>
> Hmm, it builds here - Could you post your .config?
>
Hi Peter,
I tried installing buildroot on a fresh machine but got the same error
so I don't think it's my machine.
I did a new git clone and then git checkout of this commit:
473a91dbe660cd7b0e56b4afc18121da52c89492 now Qt builds. There are about
a dozen qt specific commits that follow the one above, when I get some
time later this week I'll try to find which change caused the problem.
Regards.
--
Ormund Williams
OrmLab LLC
next prev parent reply other threads:[~2009-12-02 23:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 20:37 [Buildroot] Qt fails to build Ormund Williams
2009-11-15 19:36 ` Peter Korsgaard
2009-11-15 20:28 ` Ormund Williams
2009-12-02 23:44 ` Ormund Williams [this message]
2009-12-03 10:31 ` Peter Korsgaard
2009-12-03 22:26 ` Ormund Williams
2009-12-04 0:38 ` Thiago A. Corrêa
2010-01-04 9:43 ` alexperl
2010-01-05 1:19 ` Ormund Williams
2010-01-05 13:27 ` alexperl
2010-01-05 14:09 ` alexperl
2010-01-05 16:58 ` Ormund Williams
2010-01-05 16:55 ` Ormund Williams
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=1259797454.1750.34.camel@station1.ormlab.com \
--to=ormundw@panix.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